chore(security): .trivyignore entries have expired

Open
#222 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
devops, security

Research direction

Start with .trivyignore and .github/workflows/trivyignore-expiration.yml to understand the expired entries and how they are generated. Check upstream fixes for each listed CVE, then either remove entries after updating the affected image or dependency, or extend each still-needed expiry with a fresh rationale. Done means all five entries have been reassessed and .trivyignore no longer contains expired, unjustified dates.

Written by the indexing model from the issue text.

Description

The following .trivyignore entries have passed their exp:YYYY-MM-DD date and need to be reassessed.

  • CVE-2026-28390 — expired on 2026-06-10
  • CVE-2026-28387 — expired on 2026-06-10
  • CVE-2026-28388 — expired on 2026-06-10
  • CVE-2026-28389 — expired on 2026-06-10
  • CVE-2026-31789 — expired on 2026-06-10

For each entry:

  1. Re-check upstream for a fix (new base image, new dependency release).
  2. If fixed: bump the affected image/dependency and remove the line from .trivyignore.
  3. If still unfixed and still not exploitable in our context: extend the exp: date with a fresh rationale.

Generated by .github/workflows/trivyignore-expiration.yml.

Dominant language
Go
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from strait-dev/strait

All issues in strait-dev/strait

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.