CVE-2025-8291
Description
The 'zipfile' module would not check the validity of the ZIP64 End of Central Directory (EOCD) Locator record offset value would not be used to locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be assumed to be the previous record in the ZIP archive. This could be abused to create ZIP archives that are handled differently by the 'zipfile' module compared to other ZIP implementations. Remediation maintains this behavior, but checks that the offset specified in the ZIP64 EOCD Locator record matches the expected value.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| โ | Affected | โ |
AlmaLinux Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | python-unversioned-command-3.9.25-2.el9_7.noarch.rpm |
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 3.13.5-2+deb13u1 |
| sid | Fixed | 7.3.21+dfsg-1 |
| forky | Fixed | 7.3.21+dfsg-1 |
| bullseye | Fixed | 7.3.5+dfsg-2+deb11u5 |
| bookworm | Fixed | 3.11.2-6+deb12u7 |
Red Hat Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | โ |
| 8 | Fixed | โ |
Rocky Linux Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | โ |
| 8 | Fixed | โ |
References
- https://errata.rockylinux.org/RLSA-2026:0123
- https://errata.rockylinux.org/RLSA-2025:23530
- https://access.redhat.com/errata/RHSA-2025:23323
- https://access.redhat.com/errata/RHSA-2025:23342
- https://bugzilla.redhat.com/2294682
- https://bugzilla.redhat.com/2373234
- https://bugzilla.redhat.com/2402342
- https://bugzilla.redhat.com/2408891
- https://errata.almalinux.org/9/ALSA-2025-23342.html
- https://security-tracker.debian.org/tracker/CVE-2025-8291
- https://www.suse.com/security/cve/CVE-2025-8291.html
- https://errata.rockylinux.org/RLSA-2025:23323
- https://errata.rockylinux.org/RLSA-2025:23342
- https://errata.almalinux.org/9/ALSA-2025-23323.html
- https://access.redhat.com/errata/RHSA-2026:0123
- https://bugzilla.redhat.com/2418655
- https://errata.almalinux.org/8/ALSA-2026-0123.html
- https://access.redhat.com/errata/RHSA-2025:23530
- https://bugzilla.redhat.com/2321440
- https://bugzilla.redhat.com/2325776
- https://bugzilla.redhat.com/2343237
- https://bugzilla.redhat.com/2366509
- https://bugzilla.redhat.com/2370010
- https://bugzilla.redhat.com/2370014
- https://bugzilla.redhat.com/2370016
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.