Skip to main content
Menu
CVEs

CVE

GLPI auth bypass in two-factor settings

CVE-2026-57151EUVD-2026-126647

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 11.0.10, 12.0.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 11.0.10, 12.0.1.

Published
Last modified
Reference
Last checked
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

GLPI, an IT asset and management software package, has a flaw in versions from 11.0.0 up to 11.0.10 and 12.0.1 that lets an authenticated technician change the two-factor authentication settings of a user with higher privileges, disabling that protection or taking control of it. The attack can be launched remotely over the network, but the attacker must already be logged in with a technician account.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

GLPI is a free asset and IT management software package. From 11.0.0 until 11.0.10 and 12.0.1, an authenticated technician can modify the two-factor authentication security of a user with higher privileges because the affected operations do not enforce all required authorization checks for the target user. This allows the technician to disable or take control of the higher-privileged user's two-factor authentication protection. This issue is fixed in versions 11.0.10 and 12.0.1.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 11.0.10, 12.0.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-57151 (GLPI: 2FA deactivation of users with higher privileges), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-57151 (entry last updated 2026-11-16):
Affected:
- glpi-project glpi: from 11.0.0, fixed in 11.0.10; from 12.0.0, fixed in 12.0.1
Fixed versions: 11.0.10, 12.0.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-57151 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-57151 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/glpi-project/glpi/security/advisories/GHSA-mhhg-77qx-qf26
- https://github.com/glpi-project/glpi/commit/c31c053b31950335f4f574b4c85dd0a07623b780
- https://github.com/glpi-project/glpi/releases/tag/11.0.10
- https://github.com/glpi-project/glpi/releases/tag/12.0.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-57151
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-57151"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • glpi-project glpi

    From 11.0.0 · fixed in 11.0.10; From 12.0.0 · fixed in 12.0.1

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-57151

Is CVE-2026-57151 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-57151?

glpi: from 11.0.0 before 11.0.10; from 12.0.0 before 12.0.1.Source: cve.now feed data

How do I fix CVE-2026-57151?

Upgrade to a fixed version: 11.0.10, 12.0.1.Source: cve.now feed data