Bug 2362282 - CVE-2025-43859 python-h11: h11 accepts some malformed Chunked-Encoding bodies [epel-8]
Summary: CVE-2025-43859 python-h11: h11 accepts some malformed Chunked-Encoding bodies...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-h11
Version: epel8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Robby Callicotte
QA Contact:
URL:
Whiteboard: {"flaws": ["c418f5c1-d1cb-4753-8088-4...
Depends On:
Blocks: CVE-2025-43859
TreeView+ depends on / blocked
 
Reported: 2025-04-25 10:55 UTC by Michal Findra
Modified: 2025-05-11 01:53 UTC (History)
3 users (show)

Fixed In Version: python-h11-0.13.0-2.el8
Clone Of:
Environment:
Last Closed: 2025-05-11 01:53:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Findra 2025-04-25 10:55:00 UTC
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2362162

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Comment 1 Fedora Update System 2025-05-02 02:46:19 UTC
FEDORA-EPEL-2025-25fef5a8e3 (python-h11-0.13.0-2.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-25fef5a8e3

Comment 2 Fedora Update System 2025-05-03 03:00:55 UTC
FEDORA-EPEL-2025-25fef5a8e3 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-25fef5a8e3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2025-05-11 01:53:41 UTC
FEDORA-EPEL-2025-25fef5a8e3 (python-h11-0.13.0-2.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.