dbcve.org
GlpiApplication · Glpi Project

CVE-2026-22247

CRITICAL · 9.1 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 11.0.5 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GLPI is a free asset and IT management software package. From version 11.0.0 to before 11.0.5, a GLPI administrator can perform SSRF request through the Webhook feature. This issue has been patched in version 11.0.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GLPI versions 11.0.0 through 11.0.4 contain a Server-Side Request Forgery (SSRF) vulnerability in the Webhook feature that allows authenticated GLPI administrators to cause the server to make arbitrary HTTP requests to internal or external resources. This can enable access to internal services, cloud metadata endpoints, or internal network infrastructure.

MitigationUpgrade GLPI to version 11.0.5 or later. If immediate patching is not feasible, limit administrative access to trusted users only and implement network segmentation or egress filtering to restrict outbound requests from the GLPI server.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GlpiApplication
Affected:>= 11.0.0, < 11.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify GLPI version is in affected range
    Check the installed GLPI version by accessing the About page in the GLPI administration panel or by examining the version file in the GLPI installation directory. Compare the version number to the affected range: >= 11.0.0 and < 11.0.5.
    Affected if The installed version is 11.0.0, 11.0.1, 11.0.2, 11.0.3, or 11.0.4.
  2. Confirm Webhook feature is accessible
    Log in as an administrator and navigate to the Webhook configuration section in the GLPI administration panel. Verify if the Webhook feature is present and accessible in the menu structure.
    Affected if The Webhook feature menu item exists and is accessible to administrator accounts.
  3. Review existing webhook configurations
    Examine the Webhook configuration panel to see if any webhooks have been created. Look for webhook entries that specify target URLs.
    Affected if One or more webhooks are configured with arbitrary URL targets.
  4. Audit server outbound connections
    Review server logs, proxy logs, or network traffic for outbound HTTP/HTTPS requests originating from the GLPI server. Look for requests to internal IP ranges, localhost, cloud metadata endpoints (e.g., 169.254.169.254), or unexpected external domains.
    Affected if Outbound requests from the GLPI server are observed to internal infrastructure or unauthorized external destinations.

A user is affected if their GLPI installation is version 11.0.0 through 11.0.4, the Webhook feature is accessible to their administrator account, and either webhooks are configured or suspicious outbound requests have been made from the server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.0.5 or later
Fixed in 11.0.5
Interim mitigation

Upgrade GLPI to version 11.0.5 or later. If immediate patching is not feasible, limit administrative access to trusted users only and implement network segmentation or egress filtering to restrict outbound requests from the GLPI server.

Recommended fix High confidence

GLPI 11.0.5

  1. 1. Back up your GLPI database and files before proceeding with the upgrade.
  2. 2. Download GLPI version 11.0.5 from the official GLPI repository or website.
  3. 3. Replace the existing GLPI installation files with the new version 11.0.5 files.
  4. 4. Run the GLPI upgrade process by accessing the application in a web browser and following the upgrade wizard, or use the command-line upgrade method if available.
  5. 5. Verify that the upgrade completed successfully by checking the GLPI version in the administration panel.
  6. 6. Test the Webhook functionality to ensure it works correctly after the upgrade.
  7. 7. Review GLPI logs to confirm there are no errors related to the upgrade or the Webhook feature.
Caveat Review GLPI 11.0.5 release notes for any breaking changes or migration requirements before upgrading; always backup before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22247 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data