REDHAT-BUG-2577917: Low severity Red Hat certmonger vulnerability

Published Nov 20, 2026
·
Updated

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.

Affected Software

1 affected component
Red Hat certmonger

Event History

Nov 20, 2026
Data Sourced
via Red Hat·08:42 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Hosts running the certmonger daemon that use SCEP and fetch certificate authority replies over HTTP are exposed. The risk includes connections to a malicious or compromised CA and plaintext SCEP channels where a man-in-the-middle can alter replies.

2

What does an attacker need to do to trigger the availability impact?

The attacker needs control of the CA response, either as the CA or through interception of a plaintext HTTP SCEP connection. They can send an excessively large response or deliberately serve the response slowly.

3

What operational symptoms indicate possible exploitation or exposure?

Certificate requests may remain stuck indefinitely, particularly when replies are served slowly. Once the daemon-side buffer cap is reached, requests can become permanently stuck while consuming a pinned CPU core; excessive memory consumption may also occur because response data is held in multiple copies.

4

What is the maximum size of an individual buffered response?

Per-buffer growth is bounded by the talloc allocator's 256 MiB maximum. However, the response can exist in several copies across the helper, certmonger daemon, and postprocessing child, so total memory consumption can be higher.

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