CVE-2026-133622: Certmonger: missing size limits and timeouts in scep ca reply handling lead to denial of service

Published Nov 20, 2026
·
Updated

A flaw was found in certmonger. This vulnerability allows a malicious certificate authority or an attacker positioned on an unencrypted network to cause a Denial of Service (DoS) by sending oversized or deliberately slow responses. Certmonger fails to enforce size limits or transfer timeouts when downloading and buffering Simple Certificate Enrollment Protocol (SCEP) replies over HTTP. Consequently, an attacker can exhaust host memory, drive CPU usage to capacity, or cause certificate requests to hang indefinitely.

Other sources

A flaw was found in certmonger's SCEP handling. Certificate authority replies fetched over HTTP are buffered in full before any validation, with no size limit or transfer timeout on the download, and the daemon likewise reads submit helper output into a buffer without a cap. A malicious or compromised certificate authority, or a man-in-the-middle on a plaintext SCEP channel, can use this to consume memory on the host running the certmonger daemon (per-buffer growth is bounded at the talloc allocator's 256 MiB maximum, but the data is held in several copies at once across the helper, the daemon, and its postprocessing child), to leave certificate requests permanently stuck with a pinned CPU core once the daemon-side buffer cap is reached, and to hang requests indefinitely by serving replies slowly. The impact is availability only.

— Red Hat

Affected Software

1 affected component
Red Hat certmonger

Event History

Nov 20, 2026
Data Sourced
via Red Hat·08:42 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·08:57 AM
Data Sourced
via MITRE·08:57 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:20 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial-of-service condition?

Hosts running the certmonger daemon that retrieve SCEP certificate authority replies over HTTP are exposed. The threat is most direct when the configured CA is malicious or compromised, or when SCEP uses an unencrypted network path where an attacker can modify replies.

2

Does exploitation require credentials or user interaction?

No privileges or user interaction are required according to the supplied vector. However, exploitation requires control of the CA response or a man-in-the-middle position on a plaintext SCEP connection, and the attack complexity is rated high.

3

What operational effects could indicate exploitation?

Certificate requests may hang indefinitely, while host memory consumption or CPU use can rise substantially. Oversized replies are buffered before validation; individual talloc allocations are bounded at 256 MiB, but response data can exist in multiple copies across the helper, daemon, and postprocessing child.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203