Skip to content

chore(security): review the acl exception due on 2026-11-30 - #87

Merged
maksimtech merged 2 commits into
mainfrom
chore/security-upkeep
Nov 17, 2026
Merged

maksimtech merged 2 commits into
mainfrom
chore/security-upkeep

Conversation

@maksimtech

Copy link
Copy Markdown
Owner

Why

On 2026-11-30 exceptions in SECURITY-EXCEPTIONS.toml reach their review date, and from 2026-12-01 Security Posture would have failed on its own in every Radar. This pull request is that review, plus two gaps the 2026-11-16 audit found.

What

The one entry due on 2026-11-30:

  • acl, CVE-2026-54369 (Trivy): moved to 2027-01-31. It is still no-dsa for trixie (Debian bug 1141110), and acl 2.4.0 is only in forky and sid. trixie-proposed-updates has nothing for it, and the last point release is still 13.7 of 2026-09-12, so the fix can only come with 13.8, which is due.

Security Posture gives no verdict on a failed Docker Scout scan. It ran on every Scout workflow_run, failed ones included. On 2026-11-16 exeradar's Scout stopped on a 403 before scanning, and the gate went green on the previous scan's alerts. It now runs on a workflow_run only when the scan succeeded, as exeradar#39 does. Push, PR, schedule and manual runs are unchanged. Test: test_a_failed_scan_triggers_no_verdict.

Dependabot reads uv.lock for security updates. patchradar's uv.lock held opentelemetry-api 1.45.1 with a Dependabot alert from 2026-11-14, and no pull request came, because no entry of dependabot.yml read uv.lock. A uv entry with open-pull-requests-limit: 0 stops version updates for uv, so pip's remain the one weekly stream; security updates are not limited by it. Test: test_uv_lock_gets_security_updates_and_no_version_updates.

Verification

  • This Radar's own gate, tools/security_exceptions.review, run on the new file against the live code scanning alerts of main (50 open, plus fixed and dismissed):
    • 2026-11-17: 0 unexplained, 0 expired, 0 unused.
    • 2026-12-01: 0 unexplained, 0 expired, 0 unused.
    • 2027-01-01: the entries dated 2026-12-31 expire, which is the next review (20 entries in all).
  • The new tests failed first; the full suite passes locally and ruff is clean.

🤖 Generated with Claude Code

maksimtech and others added 2 commits November 17, 2026 14:32
Security upkeep after the 2026-11-16 audit: review the acl exception due on 2026-11-30; no posture verdict on a failed Scout scan; Dependabot reads uv.lock.

The exceptions were read again on 2026-11-17 against the Debian
security tracker and archive, and against the image; run on the live
alerts, this Radar's own gate is green on 2026-11-17 and 2026-12-01.
Details per entry in the CHANGELOG and in the entries themselves.

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

codspeed Bot commented Nov 17, 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/security-upkeep (a0c844a) with main (b692117)

Open in CodSpeed

@codecov

codecov Bot commented Nov 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@sonarqubecloud

Copy link
Copy Markdown

@maksimtech
maksimtech merged commit 4a9e4a0 into main Nov 17, 2026
23 checks passed
@maksimtech
maksimtech deleted the chore/security-upkeep branch November 17, 2026 14:03
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