Skip to content
VulniPulse
Advisory severityMedium4.8Vendor: LowRed Hat Linux

Medium [CVE-2026-50269] CRLF injection in multipart headers

This medium-severity Red Hat Linux advisory covers CVE-2026-50269 affecting Exploit Intelligence, Migration Toolkit for Applications 8, OpenShift Lightspeed.

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

CVE-2026-50269 Source published Source updated

VulniPulse record published Record updated

CVE-2026-50269
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.0, attacker-controlled input included into multipart/payload headers can be used to modify a request to inject additional headers or similar.

In the unlikely situation that an application is passing user-controlled strings into MultipartWriter.append(headers=...) or Payload.headers, then an attacker may be able to modify the request to inject headers or change the contents of the request. This vulnerability is fixed in 3.14.0.

This vulnerability, known as CRLF (Carriage Return Line Feed) injection, allows an attacker to modify HTTP requests by injecting malicious input into multipart or payload headers.

If an application processes user-controlled data in these headers, an attacker could potentially alter the request's content or inject new headers, leading to unintended application behavior.

This Low impact flaw in aiohttp arises from CRLF injection when applications pass untrusted, attacker-controlled input directly into `MultipartWriter.append(headers=...)` or `Payload.headers`.

Exploitation is unlikely in typical Red Hat deployments unless custom applications are specifically configured to include unvalidated user input in these HTTP multipart or payload headers, potentially allowing an attacker to inject arbitrary HTTP headers.

Is CVE-2026-50269 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-50269 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-50269?

Upgrade to a fixed release named by Red Hat:

  • 3.14.0

Confirm against the vendor advisory before you patch.

Affected versions
  • < 3.14.0

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

Fixed versions
  • 3.14.0

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

Mitigation checklist

Recommended fix / mitigation
  • Sanitize any user-controlled input before passing it to aiohttp's `MultipartWriter.append(headers=...)` or `Payload.headers` methods. Ensure that CRLF characters (carriage return and line feed) are stripped or rejected from header values.

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

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux 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 34 official vendor sources and 160+ reviewed platform categories.

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.