File disclosure via unauthenticated path traversal
Published Aug 17, 2026 · Updated Aug 18, 2026
Path traversal in the trajectory inspector in SWE-agent 1.1.0 and earlier allows remote attackers to read off-directory trajectory JSON files via crafted /trajectory/ requests. The do_GET handler strips the /trajectory/ prefix and passes the remainder to serve_file_content, which joins it to traj_dir with Path(self.traj_dir) / file_path and opens it with json.load without verifying that the resolved path remains under the intended directory. The inspector listens on all interfaces, sends Access-Control-Allow-Origin: *, and performs no authentication, but disclosure is bounded to JSON files shaped like SWE-agent trajectories, which can expose repository contents, command output, and secrets.
Summary
What happened
Path traversal in the trajectory inspector in SWE-agent 1.1.0 and earlier allows remote attackers to read off-directory trajectory JSON files via crafted /trajectory/ requests. The do_GET handler strips the /trajectory/ prefix and passes the remainder to serve_file_content, which joins it to traj_dir with Path(self.traj_dir) / file_path and opens it with json.load without verifying that the resolved path remains under the intended directory. The inspector listens on all interfaces, sends Access-Control-Allow-Origin: *, and performs no authentication, but disclosure is bounded to JSON files shaped like SWE-agent trajectories, which can expose repository contents, command output, and secrets.
The record
- CVE
- CVE-2026-75482
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- SWE-agent
- Product
- SWE-agent
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Issue #1472 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo