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.
13322 vulnerabilities reference this CWE, most recent first.
GHSA-J37R-7F58-PM68
Vulnerability from github – Published: 2022-05-18 00:00 – Updated: 2022-05-27 00:01D-LINK DIR-825 AC1200 R2 is vulnerable to Directory Traversal. An attacker could use the "../../../../" setting of the FTP server folder to set the router's root folder for FTP access. This allows you to access the entire router file system via the FTP server.
{
"affected": [],
"aliases": [
"CVE-2022-29332"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-05-17T14:15:00Z",
"severity": "MODERATE"
},
"details": "D-LINK DIR-825 AC1200 R2 is vulnerable to Directory Traversal. An attacker could use the \"../../../../\" setting of the FTP server folder to set the router\u0027s root folder for FTP access. This allows you to access the entire router file system via the FTP server.",
"id": "GHSA-j37r-7f58-pm68",
"modified": "2022-05-27T00:01:07Z",
"published": "2022-05-18T00:00:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-29332"
},
{
"type": "WEB",
"url": "https://github.com/Quadron-Research-Lab/Hardware-IoT/blob/main/d-link_dir-825_R2.pdf"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-J383-35PM-C5H4
Vulnerability from github – Published: 2022-04-13 00:00 – Updated: 2022-04-26 21:51Grunt prior to version 1.5.2 is vulnerable to path traversal.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "grunt"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.5.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-0436"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2022-04-26T21:51:41Z",
"nvd_published_at": "2022-04-12T21:15:00Z",
"severity": "MODERATE"
},
"details": "Grunt prior to version 1.5.2 is vulnerable to path traversal.",
"id": "GHSA-j383-35pm-c5h4",
"modified": "2022-04-26T21:51:41Z",
"published": "2022-04-13T00:00:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-0436"
},
{
"type": "WEB",
"url": "https://github.com/gruntjs/grunt/pull/1743"
},
{
"type": "WEB",
"url": "https://github.com/gruntjs/grunt/commit/aad3d4521c3098fb255fb2db8f2e1d691a033665"
},
{
"type": "WEB",
"url": "https://github.com/gruntjs/grunt/commit/b0ec6e12426fc8d5720dee1702f6a67455c5986c"
},
{
"type": "PACKAGE",
"url": "https://github.com/gruntjs/grunt"
},
{
"type": "WEB",
"url": "https://huntr.dev/bounties/f55315e9-9f6d-4dbb-8c40-bae50c1ae92b"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2023/04/msg00008.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Path Traversal in Grunt"
}
GHSA-J383-PFWR-RVJW
Vulnerability from github – Published: 2022-05-01 18:40 – Updated: 2022-05-01 18:40Directory traversal vulnerability in include/file_download.php in LearnLoop 2.0 beta7 allows remote attackers to read arbitrary files via a .. (dot dot) in the sFilePath parameter. NOTE: exploitation requires that the product is configured, but has zero files in the database.
{
"affected": [],
"aliases": [
"CVE-2007-6214"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2007-12-04T15:46:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in include/file_download.php in LearnLoop 2.0 beta7 allows remote attackers to read arbitrary files via a .. (dot dot) in the sFilePath parameter. NOTE: exploitation requires that the product is configured, but has zero files in the database.",
"id": "GHSA-j383-pfwr-rvjw",
"modified": "2022-05-01T18:40:46Z",
"published": "2022-05-01T18:40:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2007-6214"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/38776"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/4680"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/26651"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-J38M-7Q52-FGFH
Vulnerability from github – Published: 2018-07-23 23:33 – Updated: 2023-09-05 23:28Affected versions of node-server-forfront resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
Recommendation
No patch is available for this vulnerability.
It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "node-server-forfront"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.10.7"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2017-16124"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:41:47Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "Affected versions of `node-server-forfront` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.",
"id": "GHSA-j38m-7q52-fgfh",
"modified": "2023-09-05T23:28:26Z",
"published": "2018-07-23T23:33:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-16124"
},
{
"type": "WEB",
"url": "https://github.com/JacksonGL/NPM-Vuln-PoC/tree/master/directory-traversal/node-server-forfront"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-j38m-7q52-fgfh"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/advisories/382"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Directory Traversal in node-server-forfront"
}
GHSA-J38X-P248-237V
Vulnerability from github – Published: 2026-04-16 09:31 – Updated: 2026-04-16 09:31The Career Section plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Path Traversal and Arbitrary File Deletion in all versions up to, and including, 1.6. This is due to missing nonce validation and insufficient file path validation on the delete action in the 'appform_options_page_html' function. This makes it possible for unauthenticated attackers to delete arbitrary files on the server via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link.
{
"affected": [],
"aliases": [
"CVE-2025-14868"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-16T08:16:26Z",
"severity": "HIGH"
},
"details": "The Career Section plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Path Traversal and Arbitrary File Deletion in all versions up to, and including, 1.6. This is due to missing nonce validation and insufficient file path validation on the delete action in the \u0027appform_options_page_html\u0027 function. This makes it possible for unauthenticated attackers to delete arbitrary files on the server via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link.",
"id": "GHSA-j38x-p248-237v",
"modified": "2026-04-16T09:31:44Z",
"published": "2026-04-16T09:31:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-14868"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3474216/career-section"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/84936b68-923a-4da1-ae67-1d63d025342e?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-J39H-M6W2-6X67
Vulnerability from github – Published: 2022-05-02 03:31 – Updated: 2022-05-02 03:31Directory traversal vulnerability in the JoomlaPraise Projectfork (com_projectfork) component 2.0.10 for Joomla! allows remote attackers to read arbitrary files via directory traversal sequences in the section parameter to index.php.
{
"affected": [],
"aliases": [
"CVE-2009-2100"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-06-17T17:30:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in the JoomlaPraise Projectfork (com_projectfork) component 2.0.10 for Joomla! allows remote attackers to read arbitrary files via directory traversal sequences in the section parameter to index.php.",
"id": "GHSA-j39h-m6w2-6x67",
"modified": "2022-05-02T03:31:40Z",
"published": "2022-05-02T03:31:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-2100"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/8946"
},
{
"type": "WEB",
"url": "http://osvdb.org/55176"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/35378"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-J3F6-5WCM-3V96
Vulnerability from github – Published: 2022-05-24 17:43 – Updated: 2022-05-24 17:43When loading a UDF, a specially crafted zip file could allow files to be placed outside of the UDF deployment directory. This issue affected Apache AsterixDB unreleased builds between commits 580b81aa5e8888b8e1b0620521a1c9680e54df73 and 28c0ee84f1387ab5d0659e9e822f4e3923ddc22d. Note: this CVE may be REJECTed as the issue did not affect any released versions of Apache AsterixDB
{
"affected": [],
"aliases": [
"CVE-2020-9479"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-03-01T16:15:00Z",
"severity": "MODERATE"
},
"details": "When loading a UDF, a specially crafted zip file could allow files to be placed outside of the UDF deployment directory. This issue affected Apache AsterixDB unreleased builds between commits 580b81aa5e8888b8e1b0620521a1c9680e54df73 and 28c0ee84f1387ab5d0659e9e822f4e3923ddc22d. Note: this CVE may be REJECTed as the issue did not affect any released versions of Apache AsterixDB",
"id": "GHSA-j3f6-5wcm-3v96",
"modified": "2022-05-24T17:43:24Z",
"published": "2022-05-24T17:43:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-9479"
},
{
"type": "WEB",
"url": "https://lists.apache.org/thread.html/r4cc9cc9c54573babf821c31d5d410fb260d1cd416dc1b225d587be9b@%3Cdev.asterixdb.apache.org%3E"
},
{
"type": "WEB",
"url": "https://www.openwall.com/lists/oss-security/2020/08/08/2"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-J3FW-WC48-29G3
Vulnerability from github – Published: 2026-05-11 14:03 – Updated: 2026-05-19 15:57** CONFIDENTIAL **
Vulnerability Disclosure Analysis Documentation
Vulnerability Details
- Discoverer: Taylor Pennington of KoreLogic, Inc.
- Date Submitted: June 11, 2024
- Title: Open WebUI Arbitrary File Write, Delete via Path Traversal
- High-level Summary: Attacker controlled files can be uploaded to arbitrary locations on the web server's filesystem by abusing a path traversal vulnerability. After the file is written, it is deleted.
- Affected Vendor: Open WebUI
- Affected Product(s): Open WebUI (Formerly Ollama WebUI)
- Affected Version(s): 0.1.105
- Platform/OS: Debian GNU/Linux 12 (bookworm)
- Vector: HTTP web interface
- CWE: 22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- Technical Analysis:
When attaching files to a prompt by clicking the plus sign (+) on the left of the message input box when using the Open WebUI HTTP interface, the file is uploaded to a static upload directory. If the file is an audio file it will be sent to a second API that will attempt to transcribe it.
The name of the file is derived from the original HTTP upload request and is not validated or sanitized. This allows for users to upload files with names containing dot-segments in the file path and traverse out of the intended uploads directory. Effectively, users can upload files anywhere on the filesystem the user running the web server has permission.
This can be visualized by examining the python code for the "/ollama/models/upload" API route (https://github.com/open-webui/open-webui/blob/0399a69b73de9789c4221acedea70d528e1346c4/backend/apps/ollama/main.py#L1063-L1127):
``` def upload_model(file: UploadFile = File(...), url_idx: Optional[int] = None): if url_idx == None: url_idx = 0 ollama_url = app.state.OLLAMA_BASE_URLS[url_idx]
file_path = f"{UPLOAD_DIR}/{file.filename}"
# Save file in chunks
with open(file_path, "wb+") as f:
for chunk in file.file:
f.write(chunk)
def file_process_stream():
nonlocal ollama_url
total_size = os.path.getsize(file_path)
chunk_size = 1024 * 1024
try:
with open(file_path, "rb") as f:
total = 0
done = False
while not done:
chunk = f.read(chunk_size)
if not chunk:
done = True
continue
total += len(chunk)
progress = round((total / total_size) * 100, 2)
res = {
"progress": progress,
"total": total_size,
"completed": total,
}
yield f"data: {json.dumps(res)}\n\n"
if done:
f.seek(0)
hashed = calculate_sha256(f)
f.seek(0)
url = f"{ollama_url}/api/blobs/sha256:{hashed}"
response = requests.post(url, data=f)
if response.ok:
res = {
"done": done,
"blob": f"sha256:{hashed}",
"name": file.filename,
}
os.remove(file_path)
yield f"data: {json.dumps(res)}\n\n"
else:
raise Exception(
"Ollama: Could not create blob, Please try again."
)
except Exception as e:
res = {"error": str(e)}
yield f"data: {json.dumps(res)}\n\n"
return StreamingResponse(file_process_stream(), media_type="text/event-stream")
```
The model is temporarily written to disk in chunks and then the data is sent to
another internal API. Once the file is successfully passed, the file is removed
from the disk. Note line 1116, `os.remove(file_path)`.
This has an affect of stomping on and ultimately deleting any file that the user
of the open-webui service has permissions over.
It may be possible to continue sending chunks to the file slowly and create
a race condition however, this was not validated.
-
Proof-of-Concept:
First, create a file under the
/tmpdirectory namedDELETE_MEwhile logged in as the user account of the web application or chown the file to be owned by the open-webui user.```
su ollama
touch /tmp/DELETE_ME
```
Execute the following cURL command after replacing the exported JWT value for a valid user session:
```
export JWT="JWT_HERE"; curl -s -X $'POST' \
-H $'Host: openwebui.example.com' -H $'Content-Length: 206' -H "Authorization: Bearer ${JWT}" -H $'Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW' \
--data-binary $'------WebKitFormBoundary7MA4YWxkTrZu0gW\x0d\x0aContent-Disposition: form-data; name=\"file\"; filename=\"../../../../../../../tmp/DELETE_ME\"\x0d\x0aContent-Type: image/png\x0d\x0a\x0d\x0a\x0d\x0a------WebKitFormBoundary7MA4YWxkTrZu0gW--' \
$'https://openwebui.example.com/ollama/models/upload'
```
Verify that `/tmp/DELETE_ME` has been deleted.
- Mitigation Recommendation: Modify line 1070 (https://github.com/open-webui/open-webui/blob/0399a69b73de9789c4221acedea70d528e1346c4/backend/apps/ollama/main.py#L1070) to:
filename = os.path.basename(file.filename)
file_path = f"{UPLOAD_DIR}/{filename}"
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.6.9"
},
"package": {
"ecosystem": "PyPI",
"name": "open-webui"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.6.10"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-44565"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-11T14:03:24Z",
"nvd_published_at": "2026-05-15T22:16:52Z",
"severity": "HIGH"
},
"details": "** CONFIDENTIAL **\n\nVulnerability Disclosure Analysis Documentation\n-----------------------------------------------\n\nVulnerability Details\n---------------------\n1. Discoverer: Taylor Pennington of KoreLogic, Inc.\n2. Date Submitted: June 11, 2024\n3. Title: Open WebUI Arbitrary File Write, Delete via Path Traversal\n4. High-level Summary:\n Attacker controlled files can be uploaded to arbitrary locations on the web\n server\u0027s filesystem by abusing a path traversal vulnerability. After the\n file is written, it is deleted.\n5. Affected Vendor: Open WebUI\n6. Affected Product(s): Open WebUI (Formerly Ollama WebUI)\n7. Affected Version(s): 0.1.105\n8. Platform/OS: Debian GNU/Linux 12 (bookworm)\n9. Vector: HTTP web interface\n10. CWE: 22 Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)\n11. Technical Analysis:\n \n When attaching files to a prompt by clicking the plus sign (+) on the left of\n the message input box when using the Open WebUI HTTP interface, the file is\n uploaded to a static upload directory. If the file is an audio file\n it will be sent to a second API that will attempt to transcribe it.\n\n The name of the file is derived from the original HTTP upload request and is\n not validated or sanitized. This allows for users to upload files with names\n containing dot-segments in the file path and traverse out of the intended\n uploads directory. Effectively, users can upload files anywhere on the\n filesystem the user running the web server has permission.\n\n This can be visualized by examining the python code for the\n \"/ollama/models/upload\" API route (https://github.com/open-webui/open-webui/blob/0399a69b73de9789c4221acedea70d528e1346c4/backend/apps/ollama/main.py#L1063-L1127):\n\n ```\n def upload_model(file: UploadFile = File(...), url_idx: Optional[int] = None):\n if url_idx == None:\n url_idx = 0\n ollama_url = app.state.OLLAMA_BASE_URLS[url_idx]\n\n file_path = f\"{UPLOAD_DIR}/{file.filename}\"\n\n # Save file in chunks\n with open(file_path, \"wb+\") as f:\n for chunk in file.file:\n f.write(chunk)\n\n def file_process_stream():\n nonlocal ollama_url\n total_size = os.path.getsize(file_path)\n chunk_size = 1024 * 1024\n try:\n with open(file_path, \"rb\") as f:\n total = 0\n done = False\n\n while not done:\n chunk = f.read(chunk_size)\n if not chunk:\n done = True\n continue\n\n total += len(chunk)\n progress = round((total / total_size) * 100, 2)\n\n res = {\n \"progress\": progress,\n \"total\": total_size,\n \"completed\": total,\n }\n yield f\"data: {json.dumps(res)}\\n\\n\"\n\n if done:\n f.seek(0)\n hashed = calculate_sha256(f)\n f.seek(0)\n\n url = f\"{ollama_url}/api/blobs/sha256:{hashed}\"\n response = requests.post(url, data=f)\n\n if response.ok:\n res = {\n \"done\": done,\n \"blob\": f\"sha256:{hashed}\",\n \"name\": file.filename,\n }\n os.remove(file_path)\n yield f\"data: {json.dumps(res)}\\n\\n\"\n else:\n raise Exception(\n \"Ollama: Could not create blob, Please try again.\"\n )\n\n except Exception as e:\n res = {\"error\": str(e)}\n yield f\"data: {json.dumps(res)}\\n\\n\"\n\n return StreamingResponse(file_process_stream(), media_type=\"text/event-stream\")\n ```\n\n The model is temporarily written to disk in chunks and then the data is sent to\n another internal API. Once the file is successfully passed, the file is removed\n from the disk. Note line 1116, `os.remove(file_path)`.\n\n This has an affect of stomping on and ultimately deleting any file that the user\n of the open-webui service has permissions over.\n\n It may be possible to continue sending chunks to the file slowly and create\n a race condition however, this was not validated.\n\n12. Proof-of-Concept:\n\n First, create a file under the `/tmp` directory named `DELETE_ME` while\n logged in as the user account of the web application or chown the file to be\n owned by the open-webui user.\n\n ```\n # su ollama\n # touch /tmp/DELETE_ME\n ```\n \n Execute the following cURL command after replacing the exported `JWT` value for a valid user session:\n\n ```\n export JWT=\"JWT_HERE\"; curl -s -X $\u0027POST\u0027 \\\n -H $\u0027Host: openwebui.example.com\u0027 -H $\u0027Content-Length: 206\u0027 -H \"Authorization: Bearer ${JWT}\" -H $\u0027Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW\u0027 \\\n --data-binary $\u0027------WebKitFormBoundary7MA4YWxkTrZu0gW\\x0d\\x0aContent-Disposition: form-data; name=\\\"file\\\"; filename=\\\"../../../../../../../tmp/DELETE_ME\\\"\\x0d\\x0aContent-Type: image/png\\x0d\\x0a\\x0d\\x0a\\x0d\\x0a------WebKitFormBoundary7MA4YWxkTrZu0gW--\u0027 \\\n $\u0027https://openwebui.example.com/ollama/models/upload\u0027\n ```\n\n Verify that `/tmp/DELETE_ME` has been deleted.\n\n13. Mitigation Recommendation: Modify line 1070 (https://github.com/open-webui/open-webui/blob/0399a69b73de9789c4221acedea70d528e1346c4/backend/apps/ollama/main.py#L1070) to: \n\n```\nfilename = os.path.basename(file.filename)\nfile_path = f\"{UPLOAD_DIR}/{filename}\"\n```",
"id": "GHSA-j3fw-wc48-29g3",
"modified": "2026-05-19T15:57:21Z",
"published": "2026-05-11T14:03:24Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/open-webui/open-webui/security/advisories/GHSA-j3fw-wc48-29g3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44565"
},
{
"type": "PACKAGE",
"url": "https://github.com/open-webui/open-webui"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Open WebUI Arbitrary File Write, Delete via Path Traversal"
}
GHSA-J3G7-CP6V-QP9F
Vulnerability from github – Published: 2026-03-16 15:30 – Updated: 2026-03-31 00:31Path traversal in Smart Switch prior to version 3.7.69.15 allows adjacent attackers to overwrite arbitrary files with Smart Switch privilege.
{
"affected": [],
"aliases": [
"CVE-2026-21005"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-16T14:18:11Z",
"severity": "HIGH"
},
"details": "Path traversal in Smart Switch prior to version 3.7.69.15 allows adjacent attackers to overwrite arbitrary files with Smart Switch privilege.",
"id": "GHSA-j3g7-cp6v-qp9f",
"modified": "2026-03-31T00:31:12Z",
"published": "2026-03-16T15:30:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-21005"
},
{
"type": "WEB",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2026\u0026month=03"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:H/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:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-J3JC-GMH7-9QR9
Vulnerability from github – Published: 2026-06-17 18:35 – Updated: 2026-06-17 18:35A vulnerability in Cisco ISE and ISE-PIC could allow an authenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials.
This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to obtain user-level access to the underlying operating system and then elevate privileges to root. In single-node deployments, successful exploitation of this vulnerability could cause the affected ISE node to become unavailable, resulting in a denial of service (DoS) condition. In that condition, endpoints that have not already authenticated would be unable to access the network until the node is restored.
{
"affected": [],
"aliases": [
"CVE-2026-20181"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-17T17:16:42Z",
"severity": "CRITICAL"
},
"details": "A vulnerability in Cisco ISE and ISE-PIC could allow an authenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials.\n\nThis vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to obtain user-level access to the underlying operating system and then elevate privileges to root. In single-node deployments, successful exploitation of this vulnerability could cause the affected ISE node to become unavailable, resulting in a denial of service (DoS) condition. In that condition, endpoints that have not already authenticated would be unable to access the network until the node is restored.",
"id": "GHSA-j3jc-gmh7-9qr9",
"modified": "2026-06-17T18:35:56Z",
"published": "2026-06-17T18:35:56Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-20181"
},
{
"type": "WEB",
"url": "https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-multi-G5WP8vv"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.