CVE-2026-75482

Received Received - Intake

Path Traversal in SWE-agent Inspector HTTP Server

Publication date: 2026-08-17

Last updated on: 2026-08-17

Assigner: VulnCheck

Description

SWE-agent's trajectory inspector (sweagent inspector), confirmed in v1.1.0, is an HTTP server that joins request paths to the trajectory directory in its /trajectory/ handler without rejecting parent-directory ('..') references, bypassing the built-in path sanitization. The server binds all interfaces (0.0.0.0), applies wildcard CORS, and requires no authentication. An unauthenticated network client (or a malicious web page via CORS) can use path traversal sequences to read files outside the intended directory. Because the read sink parses targets as trajectory JSON, disclosure is constrained to JSON files shaped like a trajectory, which can contain repository contents, command output, and secrets/API keys.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-17

Last Modified

2026-08-17

Generated

2026-08-18

AI Q&A

2026-08-18

EPSS Evaluated

N/A

NVD

CVE-2026-75482

EUVD

EUVD-2026-60394

Affected Vendors & Products

Vendor	Product	Version / Range
sweagent	swe-agent_trajectory_inspector	1.1.0

Helpful Resources

Exploitability

CWE

KEV

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.

Attack-Flow Graph

Executive Summary

This vulnerability is in SWE-agent's trajectory inspector v1.1.0, an HTTP server that improperly handles file paths. It joins request paths to the trajectory directory without blocking parent-directory references ('..'), allowing path traversal attacks. The server runs on all interfaces, enables wildcard CORS, and requires no authentication, making it accessible to unauthenticated clients or malicious web pages.

Detection Guidance

Check if the sweagent trajectory inspector is running on your network by scanning for open ports and HTTP servers. Look for responses from /trajectory/ endpoints. Use curl to test path traversal attempts like curl http://<target>/trajectory/../../../etc/passwd to see if files outside the intended directory are accessible.

Impact Analysis

An attacker could exploit this to read sensitive JSON files outside the intended directory. These files may contain repository contents, command output, secrets, or API keys. Since the server binds to all interfaces and lacks authentication, any network-accessible client could potentially access these files.

Mitigation Strategies

Disable or remove the sweagent trajectory inspector service immediately. Block external access to the HTTP server if it must run. Update to a patched version if available. Restrict network access to the server and disable CORS if not required.

Hi! I’m here to help you understand CVE-2026-75482. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70