Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,16 @@ updates:
labels:
- "dependencies"

- package-ecosystem: "uv"
directory: "/"
schedule:
interval: "weekly"
# Security updates only (tests/test_dependabot_config.py): uv.lock had a
# Dependabot alert and no pull request while no entry read it. A limit of 0
# stops version updates for uv; it does not limit security updates.
cooldown:
default-days: 14
open-pull-requests-limit: 0
- package-ecosystem: "github-actions"
directory: "/"
schedule:
Expand Down
7 changes: 7 additions & 0 deletions .github/workflows/security-posture.yml
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,13 @@ permissions:
jobs:
posture:
name: Security Posture
# Only after a scan that succeeded. A failed one read nothing: on 2026-11-16
# Docker Scout stopped on a 403 while downloading its own binary, before
# scanning (exeradar run 43925337119), and this gate ran on it anyway and went
# green on the previous scan's alerts. Skipped, it gives no verdict; the failed
# scan stays red where it is seen, and the gate speaks again when the scan
# is rerun and succeeds, or on the next push or schedule.
if: github.event_name != 'workflow_run' || github.event.workflow_run.conclusion == 'success'
runs-on: ubuntu-26.04
steps:
- name: Checkout
Expand Down
17 changes: 17 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,12 @@ what has already shipped, and for nothing else. See `RELEASING.md`.
on `main` on 2026-11-02, which had turned Security Posture red, they are recorded in
`SECURITY-EXCEPTIONS.toml` to wait for Debian, as the maintainer decided that day for every Radar.

- **The acl exception is reviewed, and runs to 2027-01-31.** CVE-2026-54369 was due on 2026-11-30,
after which Security Posture would have failed on its own. Read again on 2026-11-17: still no-dsa
for trixie (Debian bug 1141110), acl 2.4.0 only in forky and sid, nothing in
trixie-proposed-updates, and the last point release still 13.7 of 2026-09-12. The new date falls
after the 13.8 point release that is due.

### Fixed

- **The weekly mutation run gets past its stats phase again.** It had been red since 2026-10-24, four
Expand Down Expand Up @@ -103,6 +109,17 @@ what has already shipped, and for nothing else. See `RELEASING.md`.
attempts, 30 s apart) until it succeeds or names the version it could not install: the same
script, and the same `tests/test_install_from_pypi.py`, in all six Radar.

- **Security Posture gives no verdict on a failed Docker Scout scan.** It ran after every Scout 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 Scout itself does after the image workflow. Push, pull request, schedule and manual
runs are unchanged.

- **Dependabot reads `uv.lock` for security updates.** patchradar's `uv.lock` held opentelemetry-api
1.45.1 with a Dependabot alert on it from 2026-11-14, and no pull request came, because no entry
of the configuration 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, and leaves security updates to arrive.

## [2026.48] — 2026-10-24

### Security
Expand Down
7 changes: 6 additions & 1 deletion SECURITY-EXCEPTIONS.toml
Original file line number Diff line number Diff line change
Expand Up @@ -248,8 +248,13 @@ the reason has not changed.
The fix is scheduled, not absent, so the only thing to do is rebuild after the \
next trixie point release. The date below is set for that. A local TOCTOU in \
recursive setfacl/chacl; patchradar calls neither.

Reviewed 2026-11-17: still no-dsa for trixie (Debian bug 1141110). 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. Moved past the 13.8 point \
release that is due.
"""
review_by = "2026-11-30"
review_by = "2027-01-31"

[[exception]]
id = "CVE-2026-76642"
Expand Down
3 changes: 2 additions & 1 deletion docs/nis2-compliance.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,7 +230,8 @@ file letti dai test; questa revisione li aggiunge.
Sul repository sono attivi, verificato il 2026-10-11, gli avvisi Dependabot sulle
dipendenze (nessun avviso registrato a quella data) e gli aggiornamenti di sicurezza
automatici di Dependabot; `.github/dependabot.yml` chiede ogni settimana gli
aggiornamenti delle dipendenze Python, delle GitHub Actions e dell'immagine di base.
aggiornamenti delle dipendenze Python, delle GitHub Actions e dell'immagine di base;
dal 2026-11-17 legge anche `uv.lock`, solo per gli aggiornamenti di sicurezza.

Le regole del ramo `main`, lette dalle impostazioni del repository il 2026-10-12
(ruleset "main protection", attivo), impongono che ogni modifica passi da una pull
Expand Down
12 changes: 12 additions & 0 deletions tests/test_dependabot_config.py
Original file line number Diff line number Diff line change
Expand Up @@ -32,3 +32,15 @@ def test_actions_updates_arrive_as_one_pull_request():
actions = next(u for u in updates() if u["package-ecosystem"] == "github-actions")
patterns = [p for group in (actions.get("groups") or {}).values() for p in group.get("patterns", [])]
assert "*" in patterns, f"no group takes every action: {patterns}"


def test_uv_lock_gets_security_updates_and_no_version_updates():
"""patchradar's uv.lock held opentelemetry-api 1.45.1 from 2026-11-14 with a
Dependabot alert on it and no pull request: the configuration named pip and
github-actions, and none of its entries read uv.lock. A uv entry for security
updates only: open-pull-requests-limit 0 stops version updates for uv, so pip's
stay the one weekly stream, and does not limit security updates."""
uv = [u for u in updates() if u["package-ecosystem"] == "uv"]
assert len(uv) == 1, "uv.lock is not watched"
assert uv[0]["directory"] == "/"
assert uv[0]["open-pull-requests-limit"] == 0
16 changes: 16 additions & 0 deletions tests/test_scan_after_publish.py
Original file line number Diff line number Diff line change
Expand Up @@ -78,3 +78,19 @@ def test_the_customer_document_says_when_the_image_is_scanned():
doc = (WORKFLOWS.parent.parent / "docs" / "nis2-compliance.md").read_text(encoding="utf-8")
row = next(line for line in doc.splitlines() if line.startswith("| `Docker Scout` |"))
assert "ogni build dell'immagine" in row


def test_a_failed_scan_triggers_no_verdict(posture):
"""A scan that failed read nothing, so the alerts are still the previous scan's.

On 2026-11-16 Docker Scout failed on exeradar's main before scanning (a 403 while it
downloaded its own binary, run 43925337119), and the gate ran on that `workflow_run`
all the same and went green, a verdict that looked fresh and was not. This Radar had
the same trigger with no condition. Skipped instead: the failed scan stays red where it
can be seen, and the gate speaks again when the scan is rerun and succeeds, or on the
next push or schedule. As in exeradar#39.
"""
for job in posture["jobs"].values():
condition = " ".join(str(job.get("if", "")).split())
assert "github.event.workflow_run.conclusion == 'success'" in condition
assert "github.event_name != 'workflow_run'" in condition