Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-55556 – Heap Overflow / DoS – Rsyslog imhttp Module (8.2110.0–8.2603.x)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-55556 is a heap buffer overflow vulnerability in the optional imhttp input module of Rsyslog, triggered during parsing of HTTP Basic Authentication headers. An unauthenticated remote attacker can send a specially crafted, oversized Basic Authorization header to a listening imhttp endpoint to corrupt heap memory, most likely crashing the rsyslog process and interrupting log collection. The vulnerability carries a CVSS score of 8.2 (High), and only affects deployments that explicitly build, load, and configure the imhttp module with HTTP Basic Authentication enabled — it does not affect default rsyslog installations.

Technical details

  • Root cause: In contrib/imhttp/imhttp.c, the auth-header parsing function (parse_auth_header) allocates a working buffer using calloc(0, len) instead of calloc(1, len), resulting in a zero-byte heap allocation.
  • Trigger condition: When a client sends an HTTP Basic Authorization header whose base64-encoded credentials exceed the intended buffer size, apr_base64_decode() writes the fully decoded credential data into the zero-length buffer, overflowing into adjacent heap memory.
  • Attack vector: Network — a single unauthenticated HTTP request containing an oversized Basic Auth header to an exposed imhttp listener is sufficient to trigger the flaw.
  • Impact: The primary and confirmed impact is denial of service (process crash, interrupting syslog/log ingestion). The actual severity of memory corruption can vary with allocator behavior, platform, and compiler/hardening options; remote code execution has not been demonstrated.
  • Exploitation prerequisites: rsyslog must be built with the imhttp module, the module must be installed and explicitly loaded via configuration, and HTTP Basic Authentication must be enabled on the imhttp listener. Standard/default rsyslog installations, where imhttp is not loaded, are not affected.

Affected software

  • Rsyslog versions 8.2110.0 through 8.2603.x (inclusive), when built with and using the imhttp module with HTTP Basic Authentication enabled.
  • Rsyslog 8.2604.0 and later are not affected — the vulnerable authentication-parsing code was fixed/removed as part of a broader auth refactor.

Severity

  • CVSS v4.0 Base Score: 8.2 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
  • Key drivers: network-exploitable, low attack complexity, no privileges or user interaction required, high impact to availability.

Mitigation and recommended actions

  • Immediate: Upgrade Rsyslog to version 8.2604.0 or later, where the flawed allocation was corrected.
  • If upgrading is not immediately possible:
    • Apply the minimal upstream patch to affected builds, changing the buffer allocation in imhttp.c from calloc(0, len) to calloc(1, len).
    • Disable or avoid loading the imhttp module if it is not required.
    • If imhttp with Basic Authentication must remain in use, restrict network access to the imhttp listener (e.g., firewall rules, internal-only exposure) to trusted management networks until the upgrade is applied.
    • Monitor for repeated rsyslog crashes/restarts that may indicate exploitation attempts against exposed imhttp endpoints.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge