Skip to content

Update python to 3.14.8 - #789

Merged
bryan-minimal merged 3 commits into
mainfrom
update-python-3.14.8
Oct 8, 2026
Merged

bryan-minimal merged 3 commits into
mainfrom
update-python-3.14.8

Conversation

@gominimal-pkgmgr-mgr

Copy link
Copy Markdown
Contributor

Update python 3.14.7 → 3.14.8

Source: github:python/cpython:tag
Release: https://github.com/python/cpython/releases/tag/v3.14.8
Changelog: python/cpython@v3.14.7...v3.14.8
Released: 11 hours ago (2026-09-30)

Warning

Pkgscan: 1 new signal introduced by this update (risk score 2.0).
Diff against the prior version surfaced patterns that weren't present before. Review carefully before merging — supply-chain attacks land via version-bump injection.

Severity File Line Capability (MBC) Pattern
MEDIUM python (upstream release) 0 metadata/recent-bump upstream release <12h ago

Vulnerability impact

Partition analysis at 3.14.8 (uses each advisory's fixed-version, vulnerable-range, affected-ranges, and fix-commit ancestry to decide):

  • 3 cleared — the new version is outside the advisory's affected range, OR the tag's lineage includes a known fix-commit. These will drop off the next scan.
  • 5 still affecting — the new version matches the advisory's range, the fix hasn't been published, OR the advisory lacks structured range data so partition defaulted to still-affecting (the conservative pick). Rows marked ⚠ unverified are the latter case.

Vulnerabilities fixed (3)

This update clears 3 vulnerabilities affecting 3.14.7:

CVE / GHSA CPE Severity Fixed in
CVE-2026-15806 (python, python) MEDIUM via range: < 3.15.0rc2; fixed in commits a0d023f / a2773a3 / a7bb524 / 641be42 / 851cf9a
CVE-2026-17084 (python, python) MEDIUM via range: < 3.15.0rc2; fixed in commits 7e109d0 / 5181304 / 1e54caa / c016c25 / c28b121 / …
CVE-2026-15310 (python, python) LOW via range: < 3.15.0rc2; fixed in commits f897dbf / 1b424c0 / 31980e8 / e2311cf / f507e69 / …

Warning

5 known vulnerabilities still affect 3.14.8 after this update.

CVE / GHSA CPE Severity Fixed in
PSF-0000-CVE-2026-4786 (python, python) HIGH via range: fixed in commit d22922c
CVE-2025-15367 (python, python) MEDIUM via range: < 3.15.0a6; fixed in commit b234a2b
CVE-2026-87910 (python, python) MEDIUM via range: fixed in commits 9c17bac / d9565e5 / fb2f0bb; fixed in commits d9565e5 / fb2f0bb…
PSF-0000-CVE-2026-8328 (python, python) MEDIUM via range: fixed in commit eac4fe3
PSF-2026-38 (python, python) MEDIUM via range: fixed in commit 9768834

Components changed

CycloneDX component delta (declared materials — the package's own version, not a dependency-tree diff)
Component Old New
~ python 3.14.7 3.14.8
~ python-upstream 3.14.7 3.14.8

Changes

Old New
Version 3.14.7 3.14.8
SHA256 3b48dac8fb59f62e... c2215904f02b1755...
Size 24.1 MB 24.1 MB
Source gs://minimal-staging-archives/Python-3.14.7.tar.xz gs://minimal-staging-archives/Python-3.14.8.tar.xz
  • License: Python-2.0.1 (source: tarball)

Created by pkgmgr

@gominimal-pkgmgr-mgr
gominimal-pkgmgr-mgr Bot requested a review from a team as a code owner October 1, 2026 05:38
@gominimal-pkgmgr-mgr gominimal-pkgmgr-mgr Bot added the auto-update Opened autonomously by pkgmgr auto-update label Oct 1, 2026
@coderabbitai

coderabbitai Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: gominimal/pkgs/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 0d2d5746-1fda-4c2f-87ec-5e6c6761e59b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


Comment @coderabbitai help to get the list of available commands.

3.14.8's own Misc/NEWS lists gh-155999 (tarfile), gh-155694 (urllib),
gh-156002 (zipfile) and gh-155292 (stringprep); each patch reports 'previously
applied' against the 3.14.8 tree, which is what failed the build. Dropped the
four patches, their build.sh lines and build.ncl entries.

gh-157265 / CVE-2026-87910 (tarfile link-fallback filter) is NOT in 3.14.8: no
Misc/NEWS entry, and its patch still applies cleanly to the 3.14.8 tree. Kept,
with the recipe note corrected (it said 'expected in 3.14.8'). The regression
tests stay as guards, with their comments updated.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@bryan-minimal

Copy link
Copy Markdown
Member

The build on this PR failed because the recipe still carried five backport patches, and four of them are already in 3.14.8: patch reported "Reversed (or previously applied) patch detected" and exited non-zero. The bot only bumped the version, and the recipe's own notes said to drop the patches on this bump. A no-op re-run would have failed identically.

I checked each fix against the real 3.14.8 source (Python-3.14.8.tar.xz):

patch issue / CVE in 3.14.8? evidence
0001 gh-155999 tarfile, CVE-2026-19672 yes in Misc/NEWS; patch reports "previously applied"
0003 gh-155694 urllib, CVE-2026-15806 yes in Misc/NEWS; "previously applied"
0004 gh-156002 zipfile, CVE-2026-15310 yes in Misc/NEWS; "previously applied"
0005 gh-155292 stringprep, CVE-2026-17084 yes in Misc/NEWS; "previously applied"
0002 gh-157265 tarfile, CVE-2026-87910 no no Misc/NEWS entry; the patch applies cleanly to the 3.14.8 tree

So this commit drops 0001/0003/0004/0005 (files, build.sh lines, build.ncl entries) and keeps 0002: CVE-2026-87910 is still unfixed in the 3.14.8 we'd ship. The recipe note claiming it is "expected in 3.14.8" is corrected. The regression tests stay as guards with updated comments. The kept patch applies with exit 0 on a fresh 3.14.8 tree, and nickel format --check passes.

Also, PSF-0000-CVE-2026-4786 and PSF-0000-CVE-2026-8328 are false positives (placeholder ranges, already fixed in 3.14.5/3.14.6); that is fixed on the pkgmgr side (sc#479).

… gh-143923)

Fixed on main (b234a2b6, 3.15.0a6) only. The 3.14 branch has no commit touching
Lib/poplib.py after 2025-03-02 and 3.14.8's Misc/NEWS has no entry for
gh-143923, so no released 3.14.x contains it. Straight cherry-pick; applies to
the 3.14.8 tree unchanged. POP3._putcmd now raises ValueError for control
characters, so a CR/LF in a caller-supplied argument can no longer smuggle in
extra POP3 commands.

Adds a no-network regression test (poplib_rejects_control_characters) that
fails on stock 3.14.8 (all four injection shapes are sent) and passes patched.
Rewords a build.sh note that referred to the dropped patches by their old
numbers, which now clash with this 0003.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@bryan-minimal

bryan-minimal commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

Added the CVE-2025-15367 backport as 0003-gh-143923-poplib-reject-control-characters.patch (2ddcaa6a), so 3.14.8 ships fully patched against everything we track for python.

Why we carry it. gh-143923 (POP3 command injection: a CR/LF in a caller-supplied argument smuggles extra commands) was fixed on main only, in b234a2b6 (3.15.0a6). The 3.14 branch has no commit touching Lib/poplib.py after 2025-03-02, and 3.14.8's Misc/NEWS has no entry for it, so no released 3.14.x has the fix.

What it is. A straight cherry-pick of the upstream commit; it applies to the 3.14.8 tree unchanged. POP3._putcmd now raises ValueError for any control character (0x00–0x1F, 0x7F). poplib.py already imports re in 3.14.8.

Verified.

  • The exact build.sh chain (0002, then 0003) applies to a fresh 3.14.8 tree with exit 0.
  • New test poplib_rejects_control_characters (no network, exercises _putcmd): on unpatched 3.14.8 it fails, with all four injection shapes sent (\r\n, \n, \x00, \x7f); on patched poplib it passes, and a normal USER alice still goes through.
  • nickel format --check and sh -n build.sh pass.

After this, the patches the recipe carries are gh-157265 (tarfile, CVE-2026-87910) and gh-143923 (poplib, CVE-2025-15367) — both not in any released 3.14.x. Drop each on the first 3.14.x whose changelog lists it.

@bryan-minimal
bryan-minimal added this pull request to the merge queue Oct 6, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Oct 6, 2026
@bryan-minimal
bryan-minimal added this pull request to the merge queue Oct 8, 2026
Merged via the queue into main with commit 3442d78 Oct 8, 2026
11 checks passed
@bryan-minimal
bryan-minimal deleted the update-python-3.14.8 branch October 8, 2026 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-update Opened autonomously by pkgmgr auto-update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant