Skip to content

[CVE-2026-7210] Insufficient entropy in pyexpat with protection against hash flooding #149018

Closed

Activity

  1. added 2 commits that reference this issue on Jun 19, 2026
  2. tomcruiseqi commented on Jun 25, 2026

    @tomcruiseqi

    3.10 backport has been pending since the 3.13 backport landed. Would you be OK with me helping prepare the 3.10 PR based on #152188, or is it still blocked by another dependency?

  3. StanFromIreland commented on Jun 25, 2026

    @StanFromIreland
    Member

    It and 3.11/3.12 are still blocked by #151401. Are you preparing backports as a distributor? In that case I suggest you patch yourselves instead, there is no guarantee as to when we will manage to do so (see our security policy for more information).

    I see you also opened other backports that come cleanly from ones, I would ask you please avoid doing that in the future. It increases the amount of PRs we have to review, as we have no guarantee it actually backported cleanly in your case.

  4. twangboy commented on Jun 25, 2026

    @twangboy

    I realize you're busy, and python 3.10 is whenever you decide to do it. Please expedite this.

  5. StanFromIreland commented on Jun 25, 2026

    @StanFromIreland
    Member

    As documented in our security policy, distributors are responsible for patching themselves.

  6. Kanishk-Bansal commented on Aug 5, 2026

    @Kanishk-Bansal

    Is a backport for CVE-2026-7210 planned on 3.12?
    Also, is 3.12.14 expected to include all the changes merged yesterday into 3.12 master for the CVE fixes?

    CC @hartwork

  7. hartwork commented on Aug 5, 2026

    @hartwork
    ContributorAuthor

    Is a backport for CVE-2026-7210 planned on 3.12?

    @Kanishk-Bansal comment #149018 (comment) above seems related but #151401 seems to be merged by now.

    Also, is 3.12.14 expected to include all the changes merged yesterday into 3.12 master for the CVE fixes?

    I would assume so, yes, but I may be wrong.

  8. Kanishk-Bansal commented on Aug 6, 2026

    @Kanishk-Bansal

    any ETA for 3.12.14?

  9. sethmlarson commented on Aug 6, 2026

    @sethmlarson
    Contributor

    @Kanishk-Bansal As noted earlier in the thread, please see our security policy.

  10. added a commit that references this issue on Aug 11, 2026
  11. added 2 commits that reference this issue on Aug 12, 2026
  12. hartwork commented on Aug 13, 2026

    @hartwork
    ContributorAuthor

    Closing as complete…

  13. added 4 commits that reference this issue on Sep 18, 2026
  14. added 3 commits that reference this issue on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions