Skip to content
VulniPulse
Advisory severityMedium5.3Apache Software Foundation

Medium [CVE-2026-84501] unauthenticated attacker can inject arbitrary fake log lines into Apache ZooKeeper's operational log by sending a crafted add_auth("ensemble",...) request containing newline characters (\n)

This medium-severity Apache Software Foundation advisory covers CVE-2026-84501 affecting Apache ZooKeeper.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-84501 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationBig Data
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

An unauthenticated attacker can inject arbitrary fake log lines into Apache ZooKeeper's operational log by sending a crafted add_auth("ensemble",...) request containing newline characters (\n). When the ensemble name doesn't match, EnsembleAuthenticationProvider.handleAuthentication() logs the raw, unsanitized name via LOG.warn().

Because SLF4J's {} placeholder preserves embedded newlines, the attacker can forge complete log entries — with arbitrary timestamps, log levels, class names, and messages — that are visually indistinguishable from genuine ZooKeeper log output.

This issue affects Apache ZooKeeper: from 3.9.0 through 3.9.5, from 3.8.0 through 3.8.6.

Users are recommended to upgrade to version 3.8.7 or 3.9.6, which fixes the issue.

Affected versions
  • 3.9.0 through 3.9.5
  • 3.8.0 through 3.8.6.
  • through 3.8.6

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Fixed versions
  • 3.8.7
  • 3.9.6

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to version 3.8.7 or 3.9.6, which fixes the issue.

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.