CVE-2026-23624VulnerabilityPublished 4 Feb 2026

CVE-2026-23624: glpi · Session Fixation

Affects glpiSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 11.0.5 or 10.0.23 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.0.5, 10.0.23

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade glpi and glpi-project/glpi to 11.0.5 or 10.0.23.

Affected software

Product	Affected	Fixed in
glpi-projectglpi	Affected >=0.71 <10.0.23 >=11.0.0-alpha <11.0.5	Fixed in 11.0.5 10.0.23
GitHubglpi-project/glpi`pkg:github/glpi-project/glpi`Other threats	Affected >=0.71 <10.0.23 <11.0.5	Fixed in 10.0.23 11.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade GLPI installations to version 10.0.23 or 11.0.5 or later, where the vulnerability is patched. 2. If immediate upgrade is not possible, disable remote authentication via SSO variables or restrict it to trusted environments only. 3. Implement strict session management policies, including session ID regeneration upon authentication and session timeout enforcement. 4. Limit access to GLPI systems to trusted users and machines, enforcing network segmentation and access controls to reduce the risk of local or privileged attackers. 5. Monitor GLPI logs for unusual session activity or concurrent sessions from the same machine. 6. Educate users about the risks of shared workstations and encourage logging out after use. 7. Regularly audit GLPI configurations and authentication mechanisms to ensure compliance with security best practices. 8. Employ endpoint security solutions to detect and prevent unauthorized local access or privilege escalation on machines accessing GLPI.

Description

GLPI is a free asset and IT management software package. In versions starting from 0.71 to before 10.0.23 and before 11.0.5, when remote authentication is used, based on SSO variables, a user can steal a GLPI session previously opened by another user on the same machine. This issue has been patched in versions .

Impact

For European organizations, the impact of this vulnerability can be significant, especially for entities relying on GLPI for IT asset management, service desk operations, and internal workflow management. Unauthorized session hijacking can lead to exposure of sensitive asset inventories, user information, and potentially internal IT processes. This could facilitate further attacks, insider threat activities, or data leaks. Confidentiality breaches could affect compliance with GDPR and other data protection regulations, leading to legal and reputational consequences. Since the attack requires local or network-level access with some privileges, insider threats or compromised internal machines pose the greatest risk. Organizations with multi-user shared workstations or insufficient session isolation are particularly vulnerable. The medium CVSS score reflects that while the attack is not trivially exploitable remotely without privileges, the confidentiality impact is high. Disruption to IT management processes could indirectly affect operational efficiency and incident response capabilities.

CWE-384Session Fixation (opens in a new tab)
Compound weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
Architecture and Design
Invalidate any existing session identifiers prior to authorizing a new user session.
Architecture and Design
For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value.
Operation · Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
OWASP Cheat Sheets
Session Management (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Forging (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 17:44 UTC

WeaknessesCWE-384

Technical details

References

Community reviews

Related threats