Skip to content

chore(security): accept two Low OpenSSL issues of 2026-11-17 until Debian ships 3.5.10 - #93

Merged
maksimtech merged 1 commit into
mainfrom
chore/openssl-2026-11-17
Nov 18, 2026
Merged

maksimtech merged 1 commit into
mainfrom
chore/openssl-2026-11-17

Conversation

@maksimtech

Copy link
Copy Markdown
Owner

Security Posture went red on main on 2026-11-18: Docker Scout reported two new high findings against openssl 3.5.7-1~deb13u3 in the python:3.14-slim-trixie base image, none with an exception.

CVE OpenSSL rating Reached only by
CVE-2026-107493 Low an application passing its own stack to PEM_X509_INFO_read_bio_ex() and reusing it after a failed read (OpenSSL and Python's ssl never do)
CVE-2026-124709 Low a QUIC server (Python's ssl has no QUIC)
  • Source: OpenSSL security advisory of 2026-11-17; fixed upstream in 3.5.10.
  • Debian security tracker: bookworm, trixie, trixie (security) and sid vulnerable, unfixed. apt-get upgrade at build time takes the DSA at the next rebuild, and the entries then fail the gate as unused.
  • The advisory's third issue, CVE-2026-35190 (TLS 1.3 with the Suite B flag, which Python's ssl never sets), is not reported by any scanner yet, so it gets no entry now: an unused one would fail the gate.
  • review_by = "2026-12-15", with the 2026-11-10 entries.

Verification: the repository's own gate (tools/security_exceptions.py) against the live code-scanning alerts of main: 2 unexplained before, 0 after; expired on 2026-12-16 as intended. The exception and posture tests pass.

🤖 Generated with Claude Code

…bian ships 3.5.10

Docker Scout reported CVE-2026-107493 and CVE-2026-124709 as high against
openssl 3.5.7-1~deb13u3 in the python:3.14-slim-trixie base image at the
first scan of main on 2026-11-18, and Security Posture failed on two
unexplained alerts.

The OpenSSL advisory of 2026-11-17 rates both Low and fixes them in 3.5.10.
Debian lists bookworm, trixie, trixie (security) and sid as vulnerable, with
no fixed version, so there is nothing to upgrade to; `apt-get upgrade` at
build time picks the DSA up at the next rebuild, and the entries then fail
the build as unused. Neither is reachable here: one needs an application
passing its own stack to PEM_X509_INFO_read_bio_ex(), which OpenSSL and
Python's ssl never do, the other a QUIC server, which Python's ssl does not
have. The third issue of the same advisory, CVE-2026-35190, is not reported
by any scanner yet, so it has no entry: one written now would fail the gate
as unused.

Checked with the repository's own gate against the live alerts of main:
2 unexplained before, 0 after; the entries expire on 2026-12-16 with the
2026-11-10 ones.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@codecov

codecov Bot commented Nov 18, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@codspeed

codspeed Bot commented Nov 18, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

1 warning

⚠️ 11 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 17 untouched benchmarks


Comparing chore/openssl-2026-11-17 (38a1400) with main (62ad1b1)

Open in CodSpeed

@maksimtech
maksimtech merged commit ef772ed into main Nov 18, 2026
23 checks passed
@maksimtech
maksimtech deleted the chore/openssl-2026-11-17 branch November 18, 2026 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant