This CVE exposes a path traversal vulnerability in Apache InLong's Agent component, present from version 2.0.0 through 2.4.0. The Agent accepts filenames or paths from dynamic sources—user submissions, configuration, external feeds—and passes them directly to filesystem operations without enforcing structural constraints. This is a systemic API design failure: the framework made unsafe path handling the path of least resistance rather than providing canonical examples, validation helpers, or sandboxing boundaries that would make arbitrary filesystem access a deliberate deviation.
The practical impact extends far beyond local file disclosure. InLong Agents sit at ingestion edges with elevated connectivity to configuration stores, credential backends, and downstream sinks. Arbitrary file read on an Agent host exposes the certificates and credentials that gate your entire data topology. The CVSS 7.5 score measures the exploit mechanism, not the detonation radius — a compromise on an Agent node radiates outward into every system that Agent was authorized to touch.
The cherry-pick fix pattern is a red flag. The vulnerability was patched at a single call site rather than through architectural hardening — no input sanitization library, no sandboxed filesystem context, no API-level canonicalization. This leaves the same unhardened abstraction intact elsewhere in the codebase. Future developers adding filename fields will face the same path of least resistance that produced this CVE.
If you run InLong 2.3.x or earlier, treat this as priority: the patch exists, but every unpatched deployment is a disclosed-but-unfixed exposure point. Verify whether any custom Agent configurations accept dynamic path inputs and validate them at the API boundary before filesystem operations.