Skip to content

[security] Please upgrade bundled Expat to 2.7.4 (e.g. for the fixes to CVE-2026-24515 and CVE-2026-25210) #144363

Description

@hartwork

Bug report

Bug description:

Hello! 👋

Please upgrade bundled Expat to 2.7.4 (e.g. for the fixes to CVE-2026-24515 and CVE-2026-25210).

The CPython issue for previous 2.7.3 was #139312 and the related merged main pull request was #139319, in case you want to have a look. (The Dockerfile from comment #123689 (review) could be of help with raising confidence in a bump pull request when going forward.)

Thanks in advance!

CPython versions tested on:

3.9, 3.10, 3.11, 3.12, 3.13, 3.14, 3.15, CPython main branch

Operating systems tested on:

Linux, macOS, Windows, Other

Linked PRs

Activity

  1. added
    3.11only security fixes
    3.12only security fixes
    3.13only security fixes
    3.14bugs and security fixes
    3.15bugs and security fixes
    on Jan 31, 2026
  2. dkoszewski commented on Feb 4, 2026

    @dkoszewski

    Hi, do you know the usual timeline for including a newer Expat release in Python distributions? Python 3.13 and 3.14 were released yesterday, but they don’t include this upgrade. Many thanks!

  3. hartwork commented on Feb 4, 2026

    @hartwork
    ContributorAuthor

    @dkoszewski https://peps.python.org/pep-0719/#source-only-security-fix-releases reads "Provided irregularly on an as-needed basis until October 2029" which I read as "there is no usual". The key question to me would be how your distributor of CPython binaries builds CPython and whether you are even using the Expat bundled with CPython; e.g. for me system-wide Expat is used…

    # python3 -c 'import pyexpat; print(pyexpat.__file__)' | xargs -n1 lddtree | grep libexpat
        libexpat.so.1 => /usr/lib64/libexpat.so.1

    …and then the updates to system Expat are the answer.

  4. StanFromIreland commented on Feb 4, 2026

    @StanFromIreland
    Member

    I'm fairly certain we'll get it in by the next release, apologies!

  5. added a commit that references this issue on Feb 5, 2026
  6. added a commit that references this issue on Feb 5, 2026
  7. 2 remaining items

  8. added a commit that references this issue on Feb 5, 2026
  9. added 2 commits that reference this issue on Feb 5, 2026
  10. added 2 commits that reference this issue on Feb 9, 2026
  11. added a commit that references this issue on Feb 15, 2026
  12. added a commit that references this issue on Feb 23, 2026
  13. added 2 commits that reference this issue on Mar 2, 2026
  14. added a commit that references this issue on Apr 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions