CVE-2026-47118: Agent Zero < 1.15 Path Traversal File Read via image_get API
Agent Zero before version 1.15 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files by supplying crafted paths to the image file serving endpoint, which relies solely on an extension allowlist while the path containment check is explicitly disabled. Attackers can request any file with an image extension readable by the process, including files outside the agent workspace, user home directories, and mounted volumes, and can also leverage symlink-based escapes due to the lack of path canonicalization in the path resolution logic.
Security readout for executives and security teams
Plain-English summary
Agent Zero versions before 1.15 can expose files through an unauthenticated image-serving API. The bug can let an attacker read image-extension files outside the intended workspace, including from home directories or mounted volumes, if the Agent Zero process can read them.
Executive priority
Treat as urgent for internet-exposed or shared Agent Zero deployments. The business concern is data disclosure, not system takeover, but exposed configuration files, documents, or mounted data could create broader downstream risk.
Technical view
CVE-2026-47118 is a CWE-22 path traversal issue in Agent Zero's image_get API. Sources state path containment checking was disabled, extension allowlisting was relied on, and path canonicalization was missing, allowing traversal and symlink-based escapes for readable image-extension files.
Likely exposure
Exposure is most likely where Agent Zero before 1.15 is reachable over a network, especially if unauthenticated access to image retrieval is possible or sensitive directories and volumes are mounted near the agent runtime.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. The issue is still high risk because it is unauthenticated, low complexity, network-reachable, and can disclose confidential local files readable by the process.
Researcher notes
Affected version metadata is limited in the bundle, but the description states Agent Zero before 1.15. The patch reference should be reviewed for exact code changes. Do not assume non-image files are exposed unless further source evidence supports it.
Mitigation direction
Upgrade Agent Zero to version 1.15 or a vendor-patched later release.
If immediate upgrade is impossible, restrict unauthenticated network access to the affected interface.
Review and reduce mounted volumes, symlinks, and readable sensitive directories near the agent runtime.
Run Agent Zero with least-privilege filesystem permissions.
Monitor vendor and advisory pages for updated remediation guidance.
Validation and detection
Inventory Agent Zero deployments and confirm installed versions are 1.15 or later.
Check whether the image_get API is reachable from untrusted networks.
Review runtime filesystem permissions, mounted volumes, and symlink exposure.
Inspect access logs for unusual image retrieval patterns or requests referencing unexpected paths.
Confirm the patch or upgrade is deployed in production, not only in source control.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.