CVE-2026-133622: certmonger · Unthrottled Resource Allocation
Source GCVE Database
Not known to be exploited · CVSS 3.7 Low.
Data as of 20 Nov 2026, 10:34 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 3.7 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 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 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 10certmonger | Affected– | Fixed in– |
| Red Hat Enterprise Linux 6certmonger | Affected– | Fixed in– |
| Red Hat Enterprise Linux 7certmonger | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8certmonger | Affected– | Fixed in– |
| Red Hat Enterprise Linux 9certmonger | Affected– | Fixed in– |
AI-suggested
Currently, no mitigation or patch is available that meets Red Hat's criteria for ease of deployment, applicability, or stability. Systems not configured to use SCEP are not affected. Users should consider disabling SCEP enrollment if not required. Monitor Red Hat advisories for future updates or fixes.
Description
A vulnerability in certmonger allows denial of service (DoS) by sending oversized or slow SCEP replies over HTTP. Certmonger does not enforce size limits or transfer timeouts when handling these replies, which can exhaust system memory or CPU and cause certificate requests to hang. Exploitation requires a malicious certificate authority or a man-in-the-middle on an unencrypted network. The impact is limited to daemon availability and does not affect system integrity or confidentiality. SCEP enrollment is not enabled by default in typical Red Hat Enterprise Linux environments, and systems not using SCEP are unaffected. No mitigation or patch currently meets Red Hat's criteria for deployment.