CVE-2026-5078 Affecting azurite package, versions <3.35.0-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.42% (34th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-AZURITE-18584443
  • published7 Aug 2026
  • disclosed3 Jun 2026

Introduced: 3 Jun 2026

CVE-2026-5078  (opens in a new tab)

How to fix?

Upgrade Chainguard azurite to version 3.35.0-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream azurite package and not the azurite package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Impact: The morgan logging middleware's :remote-user token extracts the Basic auth username from the Authorization request header and writes it to the log stream without neutralizing control characters. An unauthenticated attacker can send a crafted Authorization Basic header containing CR or LF bytes to inject forged log lines, breaking the one-request-per-line structure of access logs and enabling log forgery against downstream log consumers. The built-in combined, common, default, and short formats are affected, as well as any custom format that references :remote-user. Affected versions: morgan 1.2.0 through 1.10.1. Patches: upgrade to morgan 1.11.0, which neutralizes control characters in the :remote-user token output. Workarounds: use a custom format string that does not include :remote-user.

CVSS Base Scores

version 3.1