Skip to main content

AIL Framework CVE-2026-59510

| EUVDEUVD-2026-41775 HIGH
Path Traversal (CWE-22)
2026-07-05 CIRCL GHSA-jf65-fx73-9f2j
7.1
CVSS 4.0 · Vendor: CIRCL
Share

Severity by source

Vendor (CIRCL) PRIMARY
7.1 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear
vuln.today AI
5.3 MEDIUM

Authenticated PDF operation gives PR:L; vendor notes additional errors must be cleared first, so AC:H; arbitrary file read yields C:H with no integrity or availability impact.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (CIRCL).

CVSS VectorVendor: CIRCL

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

1
Analysis Generated
Jul 05, 2026 - 18:21 vuln.today

DescriptionCVE.org

AIL Framework contains a path traversal vulnerability in its PDF object handling. Prior to commit 14c618fce4d1df02358717c48ea903706abecdf2, the PDF.get_filepath() function constructed a file path by joining the configured PDF storage directory with a path derived from a PDF object identifier, without verifying that the resolved path remained within the intended PDF_FOLDER directory.

An authenticated attacker able to invoke PDF object operations with a crafted identifier could use relative traversal sequences or absolute path components to cause AIL Framework to open files located outside the PDF storage directory. This could allow disclosure of files readable by the AIL process, including application configuration, credentials, or other sensitive local data. This vulnerability is potential due to additional errors before being able to be executed.

The fix canonicalises the resulting path with os.path.realpath() and rejects paths whose common directory is outside the configured PDF directory.

AnalysisAI

Path traversal in AIL Framework's PDF object handling lets an authenticated user read files outside the intended PDF storage directory. The PDF.get_filepath() function joined the configured PDF_FOLDER with an attacker-influenced object identifier without validating the resolved location, so crafted relative traversal sequences or absolute path components could point AIL at arbitrary files readable by the service account, exposing configuration, credentials, or other local secrets. No public exploit identified at time of analysis, and the vendor notes exploitation is only potential because additional errors must be overcome before the traversal executes.

Technical ContextAI

AIL Framework (Analysis Information Leak framework) is an open-source, modular threat-intelligence platform maintained by CIRCL for analysing and detecting leaked or sensitive information in unstructured data feeds. The affected component is its PDF object handler, which persists and retrieves PDF artefacts under a configured PDF_FOLDER directory. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory): PDF.get_filepath() built a filesystem path with a naive join of the storage root and a PDF object identifier, trusting that identifier as a safe relative component. Because Python's os.path.join discards the left operand when the right operand is absolute, and does not collapse '../' sequences, an identifier containing traversal or absolute-path elements escapes the intended directory. The fix canonicalises the path with os.path.realpath() and rejects any result whose common path with the configured PDF directory falls outside it.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed - update AIL Framework to a build that includes commit 14c618fce4d1df02358717c48ea903706abecdf2, which adds os.path.realpath() canonicalisation and rejects paths whose common directory lies outside the configured PDF_FOLDER (patch: https://github.com/ail-project/ail-framework/commit/14c618fce4d1df02358717c48ea903706abecdf2.patch). If immediate patching is not possible, reduce exposure by restricting who holds authenticated AIL accounts and access to PDF object operations, since exploitation requires PR:L and trimming untrusted or shared accounts directly removes attack surface. Run the AIL process under a dedicated low-privilege service account whose filesystem read permissions are scoped as tightly as possible so a successful traversal reaches only non-sensitive files, and ensure application configuration and credential files are not readable by that user where feasible - note this hardens impact but does not close the flaw and may complicate legitimate file access. Avoid exposing the AIL web interface directly to untrusted networks; front it with network ACLs or a VPN to limit reachability given the network attack vector.

Share

CVE-2026-59510 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy