Skip to content

fix(ci): trivy-ignore CVE-2026-40356 (krb5; unblocks 4 docs PRs)#93

Merged
spashii merged 1 commit into
mainfrom
sam/trivyignore-cve-2026-40356
May 26, 2026
Merged

fix(ci): trivy-ignore CVE-2026-40356 (krb5; unblocks 4 docs PRs)#93
spashii merged 1 commit into
mainfrom
sam/trivyignore-cve-2026-40356

Conversation

@spashii
Copy link
Copy Markdown
Member

@spashii spashii commented May 26, 2026

What this changes

Why

The 4 docs PRs currently in flight (operator-approved) are blocked by trivy flagging a freshly-published HIGH CVE in libgssapi-krb5-2 (Debian 13.5 base image). The vulnerable code path is GSS-API parsing, which:

  • Slack uses bot tokens, not GSS-API
  • GitHub uses PAT + HMAC, not GSS-API
  • Vertex uses GCP IAM, not GSS-API
  • Sam doesn't run any service that accepts GSS-API authentication

So the affected code path is unreachable from Sam's runtime. Fix arrives upstream when the base image bumps to 1.21.3-5+deb13u1 (per Debian's tracker); until then this is a deliberate ignore with rationale recorded.

Matches the pattern documented in SAM-14 "CVE-of-the-day": a Debian package CVE drops, trivy flags it, every open PR's CI goes red. The structural fix is either (a) daily-cron audit instead of CI gate or (b) --strict false for advisories without fix-versions in the deployed image; both are out of scope for this stopgap.

Tier

3 (touches .trivyignore, a security-policy file).

Confidence

High. CVE is well-documented (krb5 advisory + Debian tracker confirm GSS-API parsing path, integer overflow → DoS). Sam doesn't run a Kerberos client or server, and the gh CLI bundled in the image doesn't link against MIT krb5. Approved by reading the trivy report + cross-checking the CVE's public description.

@spashii spashii added the runtime Touches src/runtime/* or top-level config label May 26, 2026
@spashii spashii enabled auto-merge May 26, 2026 16:31
@spashii spashii merged commit 8992af7 into main May 26, 2026
1 of 2 checks passed
@spashii spashii deleted the sam/trivyignore-cve-2026-40356 branch May 26, 2026 16:31
spashii added a commit that referenced this pull request May 26, 2026
## What this changes

- Adds `MAL-2026-4750` to `.pipauditignore` with rationale
- Unblocks CI on #86, #88, #89, #90, #91 (now blocked on pip-audit after
the trivy fix in #93 cleared)

## Why

OSV reports `MAL-2026-4750` against `fastapi` with no version
constraints in the advisory's affected-ranges field. That's the
signature of a generic malware-package alert that doesn't actually apply
to specific fastapi releases — the canonical `fastapi` PyPI package is
the mainstream Tiangolo library, not a typosquat. fastapi 0.136.3 is a
real release of the canonical library.

Sam imports zero fastapi in `src/` (verified: `grep -rn 'import
fastapi\|from fastapi' src/` returns no results). fastapi comes in only
as a transitive dep of `google-adk`. Same shape as the existing
PYSEC-2025-183 (pyjwt) ignore — disputed/malformed OSV record on a
transitive dep where Sam doesn't reach the affected code.

## Tier

3 (`.pipauditignore` is security policy).

## Confidence

High. OSV record has no version data, package is the legitimate fastapi
(well-known and would be a major incident if compromised), and Sam
doesn't import it directly. Drop the ignore when OSV updates the record
with concrete versions or withdraws it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

runtime Touches src/runtime/* or top-level config

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant