PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-45801 glpi-project CVE debrief

An authenticated user without required permissions can enable debug mode in GLPI versions 0.72 to 10.0.26 and 11.0.8. This issue is fixed in versions 11.0.8 and 10.0.26. The vulnerability allows unauthorized access to debug mode, potentially leading to further exploitation. GLPI administrators should verify and apply patches to prevent exploitation. The issue is related to improper privilege management, allowing users to bypass intended restrictions. This could lead to unauthorized access and potential data breaches if exploited.

Vendor
glpi-project
Product
glpi
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-25
Original CVE updated
2026-09-25
Advisory published
2026-09-25
Advisory updated
2026-09-25

Who should care

GLPI administrators and users with access to the affected versions should verify and apply patches to prevent exploitation. Additionally, security teams and vulnerability management teams should review the vulnerability and apply patches to prevent exploitation. Operators and platform administrators should also review the vulnerability and apply patches to prevent exploitation.

Why it matters

CVE-2026-45801 allows authenticated users to enable debug mode in GLPI versions 0.72 to 10.0.26 and 11.0.8, potentially leading to unauthorized access.

  • Verify and apply patches for GLPI versions 0.72 to 10.0.26 and 11.0.8
  • Restrict debug mode activation to authorized users
  • Monitor GLPI systems for unauthorized debug mode activation

Technical summary

The GLPI software package allows an authenticated user without required permissions to enable debug mode in versions 0.72 to 10.0.26 and 11.0.8. This issue is related to improper privilege management, allowing users to bypass intended restrictions. The vulnerability can lead to unauthorized access and potential data breaches if exploited. The issue is fixed in versions 11.0.8 and 10.0.26. Technical details suggest that the vulnerability is related to improper validation of user permissions, allowing unauthorized access to debug mode.

Defensive priority

Defenders should prioritize verifying and applying patches for GLPI versions 0.72 to 10.0.26 and 11.0.8.

Recommended defensive actions

  • Verify GLPI version and apply patches for versions 0.72 to 10.0.26 and 11.0.8
  • Restrict debug mode activation to authorized users
  • Monitor GLPI systems for unauthorized debug mode activation
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability and affected versions. The GLPI software package has a debug mode that can be enabled by authenticated users without required permissions in versions 0.72 to 10.0.26 and 11.0.8. The issue is fixed in versions 11.0.8 and 10.0.26. Evidence from the CVE record and NVD entry suggests that the vulnerability is related to improper privilege management. Defenders should verify and apply patches to prevent exploitation.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-45801 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-45801

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-45801 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-45801

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.