{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-59510 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59510 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59510 is a high-severity path traversal vulnerability in ail-project ail-framework, published on 5 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-59510 and fix it if it is affected.\n\nWhat it is: CVE-2026-59510 is a high-severity path traversal vulnerability in ail-project ail-framework, published on 5 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-59510 in the wild and no public exploit code.\n\nAffected product: ail-project ail-framework. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59510/ (Markdown: https://insights.sbomify.com/CVE-2026-59510/index.md)","id":"CVE-2026-59510","markdown":"https://insights.sbomify.com/CVE-2026-59510/index.md","name":"CVE-2026-59510","record":{"aliases":["GHSA-jf65-fx73-9f2j"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AIL Framework","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit path traversal in PDF handling to read sensitive files outside the storage directory, requiring a patch to canonicalize paths.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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/U:Clear","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.\n\nAn 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.\n\nThe fix canonicalises the resulting path with os.path.realpath() and rejects paths whose common directory is outside the configured PDF directory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Authenticated Path Traversal in AIL Framework PDF Object Handling Enables Potential Arbitrary File Read","id":"CVE-2026-59510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Exclusive Addons Elementor plugin \u003c= 2.7.9.9 - Sensitive Data Exposure vulnerability","id":"CVE-2026-59511"},"packages":[],"prev":{"headline":"Unauthenticated arbitrary MongoDB collection read in cve-search","id":"CVE-2026-59509"},"products":["ail-framework"],"published":"2026-07-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-06","vendors":["ail-project"]},"summary":"Authenticated attackers can exploit path traversal in PDF handling to read sensitive files outside the storage directory, requiring a patch to canonicalize paths.","url":"https://insights.sbomify.com/CVE-2026-59510/"}