CVE-2026-37531
Zip Slip Path Traversal in AGL app-framework-main
Publication date: 2026-05-01
Last updated on: 2026-05-01
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| agl | app-framework-main | to 17.1.12 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | 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. |
| CWE-367 | The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the AGL app-framework-main up to version 17.1.12 and involves a Zip Slip path traversal combined with a TOCTOU (Time Of Check to Time Of Use) race condition during the widget installation process.
The function is_valid_filename attempts to validate ZIP entry names but only blocks absolute paths and does not prevent directory traversal sequences using dot notation (e.g., ../).
During extraction, the zread function uses openat with the working directory file descriptor, which resolves dot notation paths relative to the work directory, allowing files to be written anywhere on the filesystem.
Critically, the extraction happens before signature verification, so even if the signature check fails, files written outside the temporary directory via path traversal remain on the system because the cleanup only removes files inside the temporary directory.
How can this vulnerability impact me? :
This vulnerability can have severe impacts as it allows an attacker to write arbitrary files anywhere on the filesystem without proper authorization.
Because the extraction occurs before signature verification, malicious files can persist even if the signature check fails, potentially leading to unauthorized code execution, system compromise, or data corruption.
The CVSS score of 9.8 indicates a critical severity with high impact on confidentiality, integrity, and availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized file writes anywhere on the filesystem before signature verification, potentially leading to unauthorized data modification or persistence of malicious files. This can result in a high impact on confidentiality, integrity, and availability of data.
Such impacts could affect compliance with standards and regulations like GDPR and HIPAA, which require protection of sensitive data and system integrity. However, the provided information does not explicitly state the compliance implications.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediate steps should focus on preventing exploitation of the Zip Slip path traversal and TOCTOU race condition in the widget installation flow.
- Avoid using vulnerable versions of the AGL app-framework-main (up to 17.1.12) until a patch or update is available.
- Restrict or monitor the installation of widgets from untrusted sources to reduce risk of malicious ZIP files exploiting path traversal.
- Implement additional file system monitoring to detect unexpected file writes outside intended directories.
- If possible, apply patches or updates from the vendor that address the validation of ZIP entry names and ensure signature verification occurs before extraction.