{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53629 exists.","fix":"No fix has been published for CVE-2026-53629 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53629 is a high-severity SQL injection vulnerability in glpi-project glpi, published on 25 Sep 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-53629 and fix it if it is affected.\n\nWhat it is: CVE-2026-53629 is a high-severity SQL injection vulnerability in glpi-project glpi, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53629 exists.\n\nAffected product: glpi-project glpi. 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-53629/ (Markdown: https://insights.sbomify.com/CVE-2026-53629/index.md)","id":"CVE-2026-53629","markdown":"https://insights.sbomify.com/CVE-2026-53629/index.md","name":"CVE-2026-53629","record":{"aliases":["GHSA-cpcj-x335-5cmh","UBUNTU-CVE-2026-53629"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"IT asset management","requires_auth":"low_privilege","summary":"An attacker with log read access can inject SQL via the history tab URL, allowing unauthorized database access in GLPI.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","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:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"GLPI is a free asset and IT management software package. From 9.4.0 until 10.0.26 and 11.0.8, an attacker with the READ right on logs can craft a URL for the history tab that injects attacker-controlled values into a database query. This permits SQL injection through the history tab endpoint. This issue is fixed in versions 11.0.8 and 10.0.26.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-05-31","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-05-31T16:26:57Z","kind":"github_poc","ref":"https://github.com/5kr1pt/glpi-logbleed","stars":1,"title":"PoC for CVE-2026-53629, blind SQL injection in the GLPI history log filter"},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-53629.yaml","stars":null,"title":"GLPI - Blind SQL Injection in History Log Filter (LogBleed)"}],"tier":"weaponised"},"has_fix":false,"headline":"GLPI: SQL injection in history tab","id":"CVE-2026-53629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"NTLMv2 hash disclosure via UNC path handling on Windows","id":"CVE-2026-53632"},"packages":[],"prev":{"headline":"GLPI: Unallowed authentication method update by administrator","id":"CVE-2026-53628"},"products":["glpi"],"published":"2026-09-25","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-25","vendors":["glpi-project"]},"summary":"An attacker with log read access can inject SQL via the history tab URL, allowing unauthorized database access in GLPI.","url":"https://insights.sbomify.com/CVE-2026-53629/"}