CVE-2026-52848

waiting for further signalsZero needs more public information before it can validate it.

GHSA-hgr8-qvp5-mhch ↗EUVD-2026-117166 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
glpi-project glpi >= 11.0.0, < 11.0.8
fixed in 11.0.8
CWE-288 Authentication Bypass Using an Alternate Path or Channel
ETK-2026-3549Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 09msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h57m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

GLPI versions 11.0.0 through 11.0.8 are affected by a login-phase two-factor authentication bypass. An unauthenticated attacker may bypass one-time-password verification, weakening accounts protected by two-factor authentication.

mitigation

Upgrade GLPI to version 11.0.8 or later. Restrict access to the GLPI login interface until the upgrade is complete.

fixed in 11.0.8

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
25m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 22:21Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-04 22:21Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-52848

{
  "etk_id": "ETK-2026-3549",
  "cve_id": "CVE-2026-52848",
  "display_id": "CVE-2026-52848",
  "ghsa_id": "GHSA-hgr8-qvp5-mhch",
  "euvd_id": "EUVD-2026-117166",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Two-factor authentication bypass in GLPI login",
  "summary": "GLPI versions 11.0.0 through 11.0.8 are affected by a login-phase two-factor authentication bypass. An unauthenticated attacker may bypass one-time-password verification, weakening accounts protected by two-factor authentication.",
  "mitigation": "Upgrade GLPI to version 11.0.8 or later. Restrict access to the GLPI login interface until the upgrade is complete.",
  "vendor": "glpi-project",
  "product": "glpi",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 11.0.0, < 11.0.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "11.0.8"
      ],
      "package_name": "glpi",
      "purl": null
    }
  ],
  "cwes": [
    288
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.20822515,
  "t0_at": "2026-11-04T22:21:48.681000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T22:21:48.681000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T22:21:48.681000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-52848"
    }
  }
}

published 2026-11-04 22:53Z
last change 2026-11-04 23:32Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.