CVE-2026-50269: AIOHTTP: CRLF injection in multipart headers

Published Jun 15, 2026
·
Updated

Summary

Attacker-controlled input included into multipart/payload headers can be used to modify a request to inject additional headers or similar.

Impact

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.

Workaround

Sanitise such user input.

-----

Patch: https://github.com/aio-libs/aiohttp/commit/bf88077ebb14f4c29924b8e8904cba20c55c28b8

Other sources

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.

MITRE

Affected Software

2 affected componentsFixes available
pip/aiohttp<=3.13.5
3.14.0
aiohttp aiohttp<3.14.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.0
  2. Upgrade

    Upgrade aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.0Patch bf88077ebb14f4c29924b8e8904cba20c55c28b8
  3. Configuration

    If your application passes user-controlled strings into `MultipartWriter.append(headers=...)` or `Payload.headers`, sanitise those inputs to prevent CRLF injection in multipart/payload headers.

    aiohttp MultipartWriter/Payload headers user input handling for multipart/payload headers = sanitise user-controlled strings before passing them to MultipartWriter.append(headers=...) or Payload.headers

Event History

Jun 15, 2026
Advisory Published
via GitHub·08:07 PM
Data Sourced
via GitHub·08:07 PM
DescriptionWeaknessAffected Software
Jun 22, 2026
CVE Published
via MITRE·04:30 PM
Data Sourced
via MITRE·04:30 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-50269?

CVE-2026-50269 is classified with a risk score of 23.

2

What is the nature of the vulnerability in CVE-2026-50269?

CVE-2026-50269 involves attacker-controlled input in multipart/payload headers, which can lead to CRLF injection.

3

How can CVE-2026-50269 be mitigated?

To mitigate CVE-2026-50269, ensure that user inputs are properly validated and sanitized before being included in header fields.

4

Which software is affected by CVE-2026-50269?

CVE-2026-50269 affects the pip/aiohttp software library.

5

Is there an official fix for CVE-2026-50269?

Yes, updates and patches addressing CVE-2026-50269 should be released alongside newer versions of the affected software.

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