CVE-2026-54789: mod_auth_openidc · Out-of-bounds Read
Affects mod_auth_openidcSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 2.4.19.4 soon.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.19.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 17 Nov 2026.
What to do
Upgrade mod_auth_openidc and openidc/mod_auth_openidc to 2.4.19.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenIDCmod_auth_openidc | Affected
| Fixed in
|
GitHubopenidc/mod_auth_openidcpkg:github/openidc/mod_auth_openidcOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade mod_auth_openidc to version 2.4.19.4 or later where the vulnerability is fixed. No in-product workarounds exist. As a temporary measure, deploy an upstream reverse proxy or web application firewall (WAF) that rejects or normalizes malformed Cookie headers lacking '=' tokens to reduce exposure.
Description
mod_auth_openidc is an OpenID Certified authentication and authorization module for the Apache 2.x HTTP server that implements the OpenID Connect Relying Party functionality. Prior to 2.4.19.4, an out-of-bounds read and a one-byte out-of-bounds write exist in the state-cookie parser of `mod_auth_openidc`. The issue is fixed in version 2.4.19.4 by stopping the scan at the string terminator so a value-less token is rejected. No in-product workarounds are available. As a stop-gap, an upstream reverse proxy or WAF that rejects or normalizes malformed `Cookie` headers (tokens lacking `=`) can reduce exposure, but upgrading is the recommended remediation.