Compliance‑trestle’s profile import concatenates trestle:// URIs and relative file paths with the trestle_root directory and then resolves the resulting path, but it does not enforce a boundary check to keep the resolution inside the trestle workspace. This allows an attacker who supplies a crafted OSCAL profile YAML to include imports[].href values containing path‑traversal sequences, resulting in reading arbitrary files from the server filesystem. The bug (CWE‑22) can expose sensitive files, configurations, or credentials, compromising confidentiality.

The vulnerability applies to oscal‑compass compliance‑trestle library in versions 3.12.2 or earlier and 4.0.3 or earlier. Any installation that has not been updated to 3.12.3 or a newer release lacks the fix that validates import paths against the trestle workspace.

This flaw carries a CVSS score of 6.9, indicating a medium severity. No EPSS score is available and it is not listed in the CISA KEV catalog, suggesting no known exploitation yet. An attacker who can trigger the profile import—by uploading a malicious OSCAL file through the tool’s interface or API—could read any file accessible to the process. The confidentiality impact is significant, while other impacts like remote code execution are not implied.