CWE-22
Allowed-with-ReviewImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Abstraction: Base · Status: Stable
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
13025 vulnerabilities reference this CWE, most recent first.
GHSA-XH35-43PP-33V2
Vulnerability from github – Published: 2026-02-03 00:30 – Updated: 2026-03-17 15:36Vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/Rest/Handler/PageHTMLHandler.Php.
This issue affects MediaWiki: from * before 1.39.14, 1.43.4, 1.44.1.
{
"affected": [],
"aliases": [
"CVE-2025-61634"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-03T00:16:08Z",
"severity": "LOW"
},
"details": "Vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/Rest/Handler/PageHTMLHandler.Php.\n\nThis issue affects MediaWiki: from * before 1.39.14, 1.43.4, 1.44.1.",
"id": "GHSA-xh35-43pp-33v2",
"modified": "2026-03-17T15:36:17Z",
"published": "2026-02-03T00:30:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-61634"
},
{
"type": "WEB",
"url": "https://phabricator.wikimedia.org/T387478"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:M/U:Green",
"type": "CVSS_V4"
}
]
}
GHSA-XH3F-3C4F-CGH5
Vulnerability from github – Published: 2022-10-28 12:00 – Updated: 2022-11-02 19:00Honeywell Experion PKS C200, C200E, C300, and ACE controllers are vulnerable to relative path traversal, which may allow an attacker access to unauthorized files and directories.
{
"affected": [],
"aliases": [
"CVE-2021-38399"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-10-28T02:15:00Z",
"severity": "HIGH"
},
"details": "Honeywell Experion PKS C200, C200E, C300, and ACE controllers are vulnerable to relative path traversal, which may allow an attacker access to unauthorized files and directories.",
"id": "GHSA-xh3f-3c4f-cgh5",
"modified": "2022-11-02T19:00:24Z",
"published": "2022-10-28T12:00:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-38399"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/uscert/ics/advisories/icsa-21-278-04"
},
{
"type": "WEB",
"url": "https://www.honeywellprocess.com/library/support/notifications/Customer/SN2021-02-22-01-Experion-C300-CCL.pdf"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-XH3H-35F7-MGQ7
Vulnerability from github – Published: 2022-05-14 02:46 – Updated: 2025-04-20 03:31Directory traversal vulnerability in the file download functionality in ZOHO WebNMS Framework 5.2 and 5.2 SP1 allows remote attackers to read arbitrary files via a .. (dot dot) in the fileName parameter to servlets/FetchFile.
{
"affected": [],
"aliases": [
"CVE-2016-6601"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-01-23T21:59:00Z",
"severity": "HIGH"
},
"details": "Directory traversal vulnerability in the file download functionality in ZOHO WebNMS Framework 5.2 and 5.2 SP1 allows remote attackers to read arbitrary files via a .. (dot dot) in the fileName parameter to servlets/FetchFile.",
"id": "GHSA-xh3h-35f7-mgq7",
"modified": "2025-04-20T03:31:28Z",
"published": "2022-05-14T02:46:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2016-6601"
},
{
"type": "WEB",
"url": "https://blogs.securiteam.com/index.php/archives/2712"
},
{
"type": "WEB",
"url": "https://forums.webnms.com/topic/recent-vulnerabilities-in-webnms-and-how-to-protect-the-server-against-them"
},
{
"type": "WEB",
"url": "https://github.com/pedrib/PoC/blob/master/advisories/webnms-5.2-sp1-pwn.txt"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/40229"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/138244/WebNMS-Framework-5.2-SP1-Traversal-Weak-Obfuscation-User-Impersonation.html"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2016/Aug/54"
},
{
"type": "WEB",
"url": "http://www.rapid7.com/db/modules/auxiliary/admin/http/webnms_cred_disclosure"
},
{
"type": "WEB",
"url": "http://www.rapid7.com/db/modules/auxiliary/admin/http/webnms_file_download"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/539159/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/92402"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-XH64-RG4W-VMPM
Vulnerability from github – Published: 2022-05-17 01:39 – Updated: 2022-05-17 01:39Directory traversal vulnerability in asaanCart 0.9 allows remote attackers to include arbitrary local files via a .. (dot dot) in the page parameter to index.php.
{
"affected": [],
"aliases": [
"CVE-2012-5331"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-10-08T23:55:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in asaanCart 0.9 allows remote attackers to include arbitrary local files via a .. (dot dot) in the page parameter to index.php.",
"id": "GHSA-xh64-rg4w-vmpm",
"modified": "2022-05-17T01:39:48Z",
"published": "2022-05-17T01:39:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-5331"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/74065"
},
{
"type": "WEB",
"url": "http://www.exploit-db.com/exploits/18599"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/52498"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-XH68-C6F3-2HJC
Vulnerability from github – Published: 2025-09-16 00:30 – Updated: 2025-11-03 21:34A parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in macOS Sonoma 14.8, macOS Sequoia 15.7, visionOS 26, watchOS 26, macOS Tahoe 26, iOS 26 and iPadOS 26. An app may be able to access sensitive user data.
{
"affected": [],
"aliases": [
"CVE-2025-43190"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-09-15T23:15:30Z",
"severity": "MODERATE"
},
"details": "A parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in macOS Sonoma 14.8, macOS Sequoia 15.7, visionOS 26, watchOS 26, macOS Tahoe 26, iOS 26 and iPadOS 26. An app may be able to access sensitive user data.",
"id": "GHSA-xh68-c6f3-2hjc",
"modified": "2025-11-03T21:34:28Z",
"published": "2025-09-16T00:30:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-43190"
},
{
"type": "WEB",
"url": "https://support.apple.com/en-us/125108"
},
{
"type": "WEB",
"url": "https://support.apple.com/en-us/125110"
},
{
"type": "WEB",
"url": "https://support.apple.com/en-us/125111"
},
{
"type": "WEB",
"url": "https://support.apple.com/en-us/125112"
},
{
"type": "WEB",
"url": "https://support.apple.com/en-us/125115"
},
{
"type": "WEB",
"url": "https://support.apple.com/en-us/125116"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2025/Sep/53"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2025/Sep/54"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2025/Sep/55"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2025/Sep/57"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2025/Sep/58"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-XH7H-H275-6Q2F
Vulnerability from github – Published: 2025-09-22 21:30 – Updated: 2025-09-22 21:30Directory traversal vulnerability in Sync In server thru 1.1.1 allowing authenticated attackers to gain read and write access to the system via FilesManager.saveMultipart function in backend/src/applications/files/services/files-manager.service.ts, and FilesManager.compress function in backend/src/applications/files/services/files-manager.service.ts.
{
"affected": [],
"aliases": [
"CVE-2025-56869"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-09-19T16:15:45Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in Sync In server thru 1.1.1 allowing authenticated attackers to gain read and write access to the system via FilesManager.saveMultipart function in backend/src/applications/files/services/files-manager.service.ts, and FilesManager.compress function in backend/src/applications/files/services/files-manager.service.ts.",
"id": "GHSA-xh7h-h275-6q2f",
"modified": "2025-09-22T21:30:18Z",
"published": "2025-09-22T21:30:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-56869"
},
{
"type": "WEB",
"url": "https://github.com/Sync-in/server"
},
{
"type": "WEB",
"url": "https://github.com/Sync-in/server/releases/tag/v1.2.0"
},
{
"type": "WEB",
"url": "https://sync-in.com"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-XH8F-G2QW-GCM7
Vulnerability from github – Published: 2026-05-05 20:05 – Updated: 2026-06-08 23:26Impact
What kind of vulnerability is it? Who is impacted?
A path traversal vulnerability in MinIO's ReadMultiple internode storage-REST
endpoint allows a caller holding the cluster root JWT to read files from
outside the configured drive roots, bounded only by the MinIO process UID.
Distributed-erasure (multi-node) MinIO deployments are impacted. Single-node
standalone deployments do not register the route and are not affected. The
attack requires an HS512 JWT signed with MINIO_ROOT_PASSWORD and carrying
accessKey = MINIO_ROOT_USER — the same secret every peer in the cluster
holds to authenticate internode traffic, so a compromised peer or any actor in
possession of the root credential can mint one.
The ReadMultiple handler (cmd/storage-rest-server.go) decodes a msgpack
ReadMultipleReq body containing Bucket, Prefix, and Files fields and
forwards them to xlStorage.ReadMultiple (cmd/xl-storage.go) without
validation:
volumeDir := pathJoin(s.drivePath, req.Bucket) // traversal resolves here
for _, f := range req.Files {
fullPath := pathJoin(volumeDir, req.Prefix, f)
data, mt, err = s.readAllDataWithDMTime(ctx, req.Bucket, volumeDir, fullPath)
}
pathJoin calls path.Clean, which resolves .. components and produces an
absolute path anywhere on the filesystem — it is not a root jail. The global
setRequestValidityMiddleware rejects .. in r.URL.Path and r.Form but
does not inspect request bodies, so msgpack-encoded traversal bypasses it.
Sibling storage methods (StatInfoFile, ReadFileHandler, ReadVersion)
validate their volume argument through s.getVolDir(volume), which rejects
..; ReadMultiple skips this call.
The attacker sends POST /minio/storage/{drivePath}/v63/rmpl with a
msgpack-encoded body carrying ../ sequences in the Bucket field. The
server opens the resulting path via os.OpenFile with O_RDONLY|O_NOATIME
and returns its contents in the msgpack response stream.
Impact by deployment:
-
Bare-metal with
User=minioin the systemd unit — theO_NOATIMEownership check bounds the read to files owned by the MinIO UID. Reachable secrets include TLS private keys, KMS/KES key material, systemd credentials, and data belonging to other tenants sharing the same UID on the host. Secrets leaked this way persist across cluster credential rotation. -
Containerized running as UID 0 (the historical default for the official Docker image,
docker-composeexamples, and Helm charts withoutsecurityContext.runAsNonRoot) — the primitive escalates to arbitrary host-filesystem disclosure:/etc/shadow,/root/**, Kubernetes service-account tokens, cloud-init metadata caches.
Affected components: cmd/storage-rest-server.go (ReadMultiple handler),
cmd/xl-storage.go (xlStorage.ReadMultiple).
CWE: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory — 'Path Traversal')
CVSS v4.0 Score: 6.9 (Medium)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected Versions
All MinIO releases from RELEASE.2022-07-24T01-54-52Z through the final
release of the minio/minio open-source project, RELEASE.2025-09-07T16-13-09Z.
The vulnerability was introduced in commit
f939d1c18
("Independent Multipart Uploads",
PR #15346), which added the
ReadMultiple storage-REST endpoint as part of the multipart upload
redesign. The first affected release is RELEASE.2022-07-24T01-54-52Z.
Patches
Fixed in: MinIO AIStor RELEASE.2026-04-14T21-32-45Z (recommended
upgrade target). The fix — which removed the ReadMultiple handler, the
corresponding storage-driver method, the msgpack datatypes, the REST-client
wrapper, and the route registration — first shipped in MinIO AIStor
RELEASE.2024-10-23T19-38-07Z. Every AIStor release from
RELEASE.2024-10-23T19-38-07Z onward is unaffected; users should upgrade to
RELEASE.2026-04-14T21-32-45Z or later to pick up the accumulated fixes and
improvements shipped since.
Binary Downloads
| Platform | Architecture | Download |
|---|---|---|
| Linux | amd64 | minio |
| Linux | arm64 | minio |
| macOS | arm64 | minio |
| macOS | amd64 | minio |
| Windows | amd64 | minio.exe |
FIPS Binaries
| Platform | Architecture | Download |
|---|---|---|
| Linux | amd64 | minio.fips |
| Linux | arm64 | minio.fips |
Package Downloads
| Format | Architecture | Download |
|---|---|---|
| DEB | amd64 | minio_20260414213245.0.0_amd64.deb |
| DEB | arm64 | minio_20260414213245.0.0_arm64.deb |
| RPM | amd64 | minio-20260414213245.0.0-1.x86_64.rpm |
| RPM | arm64 | minio-20260414213245.0.0-1.aarch64.rpm |
Container Images
# Standard
docker pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z
podman pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z
# FIPS
docker pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z.fips
podman pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z.fips
Homebrew (macOS)
brew install minio/aistor/minio
Workarounds
If upgrading is not immediately possible:
-
Rotate the root credential and restrict who holds it. The exploit requires a JWT signed with
MINIO_ROOT_PASSWORD. Treat the root credential as the host-filesystem disclosure primitive that it is: rotate it after any suspected exposure, store it only in the secret manager that bootstraps the cluster, and do not hand it to applications or operators who only need object-level access. -
Do not run the MinIO container as UID 0. Set
securityContext.runAsNonRoot: true(and a non-zerorunAsUser) in Kubernetes manifests, or add--usertodocker run. This reduces the blast radius from arbitrary host-filesystem disclosure to MinIO-UID-owned files only. -
Restrict the internode storage-REST port at the network layer. In distributed deployments, the storage-REST route is served on the same port as the S3 API by default. Where feasible, use
--internode-portto expose internode traffic on a separate interface reachable only from other cluster peers, and block that interface from client networks.
Credits
- Finders: Discovered by Claude, Anthropic's AI assistant, and triaged by Adrian Denkiewicz at Doyensec in collaboration with Anthropic Research.
Resources
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/minio/minio"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-20220724015452"
},
{
"fixed": "0.0.0-20260414213245"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-42600"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-05T20:05:05Z",
"nvd_published_at": "2026-05-11T22:22:11Z",
"severity": "MODERATE"
},
"details": "### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nA path traversal vulnerability in MinIO\u0027s `ReadMultiple` internode storage-REST\nendpoint allows a caller holding the cluster root JWT to read files from\noutside the configured drive roots, bounded only by the MinIO process UID.\n\nDistributed-erasure (multi-node) MinIO deployments are impacted. Single-node\nstandalone deployments do not register the route and are not affected. The\nattack requires an HS512 JWT signed with `MINIO_ROOT_PASSWORD` and carrying\n`accessKey = MINIO_ROOT_USER` \u2014 the same secret every peer in the cluster\nholds to authenticate internode traffic, so a compromised peer or any actor in\npossession of the root credential can mint one.\n\nThe `ReadMultiple` handler (`cmd/storage-rest-server.go`) decodes a msgpack\n`ReadMultipleReq` body containing `Bucket`, `Prefix`, and `Files` fields and\nforwards them to `xlStorage.ReadMultiple` (`cmd/xl-storage.go`) without\nvalidation:\n\n```go\nvolumeDir := pathJoin(s.drivePath, req.Bucket) // traversal resolves here\nfor _, f := range req.Files {\n fullPath := pathJoin(volumeDir, req.Prefix, f)\n data, mt, err = s.readAllDataWithDMTime(ctx, req.Bucket, volumeDir, fullPath)\n}\n```\n\n`pathJoin` calls `path.Clean`, which resolves `..` components and produces an\nabsolute path anywhere on the filesystem \u2014 it is not a root jail. The global\n`setRequestValidityMiddleware` rejects `..` in `r.URL.Path` and `r.Form` but\ndoes not inspect request bodies, so msgpack-encoded traversal bypasses it.\nSibling storage methods (`StatInfoFile`, `ReadFileHandler`, `ReadVersion`)\nvalidate their volume argument through `s.getVolDir(volume)`, which rejects\n`..`; `ReadMultiple` skips this call.\n\nThe attacker sends `POST /minio/storage/{drivePath}/v63/rmpl` with a\nmsgpack-encoded body carrying `../` sequences in the `Bucket` field. The\nserver opens the resulting path via `os.OpenFile` with `O_RDONLY|O_NOATIME`\nand returns its contents in the msgpack response stream.\n\n**Impact by deployment:**\n\n- **Bare-metal with `User=minio` in the systemd unit** \u2014 the `O_NOATIME`\n ownership check bounds the read to files owned by the MinIO UID. Reachable\n secrets include TLS private keys, KMS/KES key material, systemd credentials,\n and data belonging to other tenants sharing the same UID on the host.\n Secrets leaked this way persist across cluster credential rotation.\n\n- **Containerized running as UID 0** (the historical default for the official\n Docker image, `docker-compose` examples, and Helm charts without\n `securityContext.runAsNonRoot`) \u2014 the primitive escalates to arbitrary\n host-filesystem disclosure: `/etc/shadow`, `/root/**`, Kubernetes\n service-account tokens, cloud-init metadata caches.\n\n**Affected components:** `cmd/storage-rest-server.go` (`ReadMultiple` handler),\n`cmd/xl-storage.go` (`xlStorage.ReadMultiple`).\n\n**CWE:** CWE-22 (Improper Limitation of a Pathname to a Restricted Directory\n\u2014 \u0027Path Traversal\u0027)\n\n**CVSS v4.0 Score:** 6.9 (Medium)\n\n**Vector:** `CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`\n\n### Affected Versions\n\nAll MinIO releases from `RELEASE.2022-07-24T01-54-52Z` through the final\nrelease of the minio/minio open-source project, `RELEASE.2025-09-07T16-13-09Z`.\n\nThe vulnerability was introduced in commit\n[`f939d1c18`](https://github.com/minio/minio/commit/f939d1c1831c71f4b1c14df6d9cd62b12ccce7a3)\n(\"Independent Multipart Uploads\",\n[PR #15346](https://github.com/minio/minio/pull/15346)), which added the\n`ReadMultiple` storage-REST endpoint as part of the multipart upload\nredesign. The first affected release is `RELEASE.2022-07-24T01-54-52Z`.\n\n### Patches\n\n**Fixed in**: MinIO AIStor `RELEASE.2026-04-14T21-32-45Z` (recommended\nupgrade target). The fix \u2014 which removed the `ReadMultiple` handler, the\ncorresponding storage-driver method, the msgpack datatypes, the REST-client\nwrapper, and the route registration \u2014 first shipped in **MinIO AIStor\n`RELEASE.2024-10-23T19-38-07Z`**. Every AIStor release from\n`RELEASE.2024-10-23T19-38-07Z` onward is unaffected; users should upgrade to\n`RELEASE.2026-04-14T21-32-45Z` or later to pick up the accumulated fixes and\nimprovements shipped since.\n\n#### Binary Downloads\n\n| Platform | Architecture | Download |\n| -------- | ------------ | --------------------------------------------------------------------------- |\n| Linux | amd64 | [minio](https://dl.min.io/aistor/minio/release/linux-amd64/minio) |\n| Linux | arm64 | [minio](https://dl.min.io/aistor/minio/release/linux-arm64/minio) |\n| macOS | arm64 | [minio](https://dl.min.io/aistor/minio/release/darwin-arm64/minio) |\n| macOS | amd64 | [minio](https://dl.min.io/aistor/minio/release/darwin-amd64/minio) |\n| Windows | amd64 | [minio.exe](https://dl.min.io/aistor/minio/release/windows-amd64/minio.exe) |\n\n#### FIPS Binaries\n\n| Platform | Architecture | Download |\n| -------- | ------------ | --------------------------------------------------------------------------- |\n| Linux | amd64 | [minio.fips](https://dl.min.io/aistor/minio/release/linux-amd64/minio.fips) |\n| Linux | arm64 | [minio.fips](https://dl.min.io/aistor/minio/release/linux-arm64/minio.fips) |\n\n#### Package Downloads\n\n| Format | Architecture | Download |\n| ------ | ------------ | ----------------------------------------------------------------------------------------------------------------------------------- |\n| DEB | amd64 | [minio_20260414213245.0.0_amd64.deb](https://dl.min.io/aistor/minio/release/linux-amd64/minio_20260414213245.0.0_amd64.deb) |\n| DEB | arm64 | [minio_20260414213245.0.0_arm64.deb](https://dl.min.io/aistor/minio/release/linux-arm64/minio_20260414213245.0.0_arm64.deb) |\n| RPM | amd64 | [minio-20260414213245.0.0-1.x86_64.rpm](https://dl.min.io/aistor/minio/release/linux-amd64/minio-20260414213245.0.0-1.x86_64.rpm) |\n| RPM | arm64 | [minio-20260414213245.0.0-1.aarch64.rpm](https://dl.min.io/aistor/minio/release/linux-arm64/minio-20260414213245.0.0-1.aarch64.rpm) |\n\n#### Container Images\n\n```bash\n# Standard\ndocker pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z\npodman pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z\n\n# FIPS\ndocker pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z.fips\npodman pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z.fips\n```\n\n#### Homebrew (macOS)\n\n```bash\nbrew install minio/aistor/minio\n```\n\n### Workarounds\n\n- [Users of the open-source `minio/minio` project should upgrade to MinIO AIStor `RELEASE.2026-04-14T21-32-45Z` or later.](https://docs.min.io/enterprise/aistor-object-store/upgrade-aistor-server/community-edition/)\n\nIf upgrading is not immediately possible:\n\n- **Rotate the root credential and restrict who holds it.** The exploit\n requires a JWT signed with `MINIO_ROOT_PASSWORD`. Treat the root credential\n as the host-filesystem disclosure primitive that it is: rotate it after any\n suspected exposure, store it only in the secret manager that bootstraps the\n cluster, and do not hand it to applications or operators who only need\n object-level access.\n\n- **Do not run the MinIO container as UID 0.** Set\n `securityContext.runAsNonRoot: true` (and a non-zero `runAsUser`) in\n Kubernetes manifests, or add `--user` to `docker run`. This reduces the\n blast radius from arbitrary host-filesystem disclosure to MinIO-UID-owned\n files only.\n\n- **Restrict the internode storage-REST port at the network layer.** In\n distributed deployments, the storage-REST route is served on the same port\n as the S3 API by default. Where feasible, use `--internode-port` to expose\n internode traffic on a separate interface reachable only from other cluster\n peers, and block that interface from client networks.\n\n### Credits\n\n- **Finders:** Discovered by Claude, Anthropic\u0027s AI assistant, and triaged by\n **Adrian Denkiewicz** at **Doyensec** in collaboration with **Anthropic\n Research**.\n\n### Resources\n\n- Introducing commit: [`f939d1c18`](https://github.com/minio/minio/commit/f939d1c1831c71f4b1c14df6d9cd62b12ccce7a3)\n ([PR #15346](https://github.com/minio/minio/pull/15346))\n- [CWE-22 \u2014 Improper Limitation of a Pathname to a Restricted Directory](https://cwe.mitre.org/data/definitions/22.html)\n- [CVE-2022-35919 \u2014 MinIO admin-authenticated path traversal in server-update endpoint (same class, different channel)](https://github.com/minio/minio/security/advisories/GHSA-gr9v-6pcm-rqvg)\n- [MinIO AIStor](https://min.io/aistor)",
"id": "GHSA-xh8f-g2qw-gcm7",
"modified": "2026-06-08T23:26:31Z",
"published": "2026-05-05T20:05:05Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/minio/minio/security/advisories/GHSA-xh8f-g2qw-gcm7"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42600"
},
{
"type": "PACKAGE",
"url": "https://github.com/minio/minio"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "MinIO vulnerable to Path Traversal via msgpack Body in `ReadMultiple` Storage-REST Endpoint"
}
GHSA-XH8M-W9H2-4FC7
Vulnerability from github – Published: 2026-05-19 18:32 – Updated: 2026-05-19 18:32An authentication bypass vulnerability exists in the embedded HTTP server of Panabit PAP-XM320 up to and including v7.7. The server validates session cookies using a filesystem existence check based on a user-controlled cookie value without proper sanitization, allowing directory traversal and bypass of authentication.
{
"affected": [],
"aliases": [
"CVE-2026-36829"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-19T17:16:22Z",
"severity": "CRITICAL"
},
"details": "An authentication bypass vulnerability exists in the embedded HTTP server of Panabit PAP-XM320 up to and including v7.7. The server validates session cookies using a filesystem existence check based on a user-controlled cookie value without proper sanitization, allowing directory traversal and bypass of authentication.",
"id": "GHSA-xh8m-w9h2-4fc7",
"modified": "2026-05-19T18:32:13Z",
"published": "2026-05-19T18:32:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-36829"
},
{
"type": "WEB",
"url": "https://secreu.notion.site/CVE-2026-36829-3652c0ab461580e19704e87b18865714"
},
{
"type": "WEB",
"url": "https://www.panabit.com"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-XH8R-PW4R-9VX4
Vulnerability from github – Published: 2022-05-17 01:52 – Updated: 2022-05-17 01:52Directory traversal vulnerability in openpam_configure.c in OpenPAM before r478 on FreeBSD 8.1 allows local users to load arbitrary DSOs and gain privileges via a .. (dot dot) in the service_name argument to the pam_start function, as demonstrated by a .. in the -c option to kcheckpass.
{
"affected": [],
"aliases": [
"CVE-2011-4122"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2011-11-17T19:55:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in openpam_configure.c in OpenPAM before r478 on FreeBSD 8.1 allows local users to load arbitrary DSOs and gain privileges via a .. (dot dot) in the service_name argument to the pam_start function, as demonstrated by a .. in the -c option to kcheckpass.",
"id": "GHSA-xh8r-pw4r-9vx4",
"modified": "2022-05-17T01:52:28Z",
"published": "2022-05-17T01:52:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-4122"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/71205"
},
{
"type": "WEB",
"url": "http://c-skills.blogspot.com/2011/11/openpam-trickery.html"
},
{
"type": "WEB",
"url": "http://openwall.com/lists/oss-security/2011/12/07/3"
},
{
"type": "WEB",
"url": "http://openwall.com/lists/oss-security/2011/12/08/9"
},
{
"type": "WEB",
"url": "http://osvdb.org/76945"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/46756"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/46804"
},
{
"type": "WEB",
"url": "http://stealth.openwall.net/xSports/pamslam"
},
{
"type": "WEB",
"url": "http://trac.des.no/openpam/changeset/478/trunk/lib/openpam_configure.c"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-XH9G-5FG8-P3WH
Vulnerability from github – Published: 2022-05-24 19:05 – Updated: 2022-05-24 19:05A CWE-22: Improper Limitation of a Pathname to a Restricted Directory vulnerability exists inIGSS Definition (Def.exe) V15.0.0.21140 and prior that could result in remote code execution, when a malicious CGF or WSP file is being parsed by IGSS Definition.
{
"affected": [],
"aliases": [
"CVE-2021-22762"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-06-11T16:15:00Z",
"severity": "HIGH"
},
"details": "A CWE-22: Improper Limitation of a Pathname to a Restricted Directory vulnerability exists inIGSS Definition (Def.exe) V15.0.0.21140 and prior that could result in remote code execution, when a malicious CGF or WSP file is being parsed by IGSS Definition.",
"id": "GHSA-xh9g-5fg8-p3wh",
"modified": "2022-05-24T19:05:03Z",
"published": "2022-05-24T19:05:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-22762"
},
{
"type": "WEB",
"url": "http://download.schneider-electric.com/files?p_Doc_Ref=SEVD-2021-159-01"
}
],
"schema_version": "1.4.0",
"severity": []
}
Mitigation MIT-5.1
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.
- Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation MIT-20.1
Strategy: Input Validation
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
- Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59). This includes:
- realpath() in C
- getCanonicalPath() in Java
- GetFullPath() in ASP.NET
- realpath() or abs_path() in Perl
- realpath() in PHP
Mitigation MIT-4
Strategy: Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
Mitigation MIT-29
Strategy: Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Mitigation MIT-17
Strategy: Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
Mitigation MIT-21.1
Strategy: Enforcement by Conversion
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
- For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-185] provide this capability.
Mitigation MIT-22
Strategy: Sandbox or Jail
- Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
- OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
- This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
- Be careful to avoid CWE-243 and other weaknesses related to jails.
Mitigation MIT-34
Strategy: Attack Surface Reduction
- Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.
- This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.
Mitigation MIT-39
- Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
- If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
- Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
- In the context of path traversal, error messages which disclose path information can help attackers craft the appropriate attack strings to move through the file system hierarchy.
Mitigation MIT-16
Strategy: Environment Hardening
When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
CAPEC-126: Path Traversal
An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.
CAPEC-64: Using Slashes and URL Encoding Combined to Bypass Validation Logic
This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
CAPEC-76: Manipulating Web Input to File System Calls
An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
CAPEC-78: Using Escaped Slashes in Alternate Encoding
This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
CAPEC-79: Using Slashes in Alternate Encoding
This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.