Ignore latest (irrelevant) CVE alert

[hggutvik]

Summary by CodeRabbit

Chores

• Added a security assessment entry for a non-exploitable vulnerability with a scheduled re-evaluation date.

[coderabbitai]

Warning

Review limit reached

@hggutvik, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 46 minutes and 5 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3f6b4cd5-4d86-4ae6-a68e-847a794f893c

📥 Commits

Reviewing files that changed from the base of the PR and between 1eada93 and c86038c.

📒 Files selected for processing (1)

• .trivyignore.yaml

📝 Walkthrough

Walkthrough

This PR adds a Trivy security ignore entry for vulnerability CVE-2026-45447 (affecting libcrypto3/libssl3), documented as not exploitable with an expiration date of 2026-06-18 for future re-evaluation.

Changes

Security vulnerability ignore configuration

Layer / File(s)	Summary
CVE-2026-45447 ignore entry .trivyignore.yaml	Adds a new vulnerabilities ignore entry for CVE-2026-45447 marked as not exploitable with an expiration date of 2026-06-18 for reassessment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Ignore latest (irrelevant) CVE alert' clearly describes the main change: adding a Trivy ignore entry for a CVE vulnerability deemed irrelevant.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch patch/new-irrelevant-cve

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.trivyignore.yaml:
- Around line 2-4: Update the Trivy ignore entry for id CVE-2026-45447 by
renaming the field "expires" to "expired_at" so Trivy's structured ignore schema
will honor the 1-week re-evaluation; keep the rationale text referencing
PKCS7_verify as-is (confirming there are no PKCS7_verify / PKCS7_* / pkcs7
references in the repo) and ensure the entry still includes the same date value
for expired_at.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 346d1409-2fda-41d5-a2a0-ef66e6a2f89c

📥 Commits

Reviewing files that changed from the base of the PR and between 84f4b14 and 1eada93.

📒 Files selected for processing (1)

• .trivyignore.yaml

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud