chore(security): remove two CVE suppressions that match nothing - #238
Merged
Conversation
The classic-httpcore entry (CVE-2026-54428 / CVE-2026-54399) and the netty entry (CVE-2026-56816) no longer suppress anything. Comparing the OWASP reports for main and for the batched-bump branch, both CVEs appear in zero modules, while genuinely suppressed CVEs (CVE-2023-36415, CVE-2026-33117) still appear under "Suppressed Vulnerabilities". NVD has narrowed both CPE ranges since the entries were added, so neither is flagged against this dependency set any more. Removed as dead weight, matching the 2026-07-07 precedent. Three suppressions remain, all expiring 2026-10-10. This is safe to reverse: the affected artifacts are still resolved (httpcore 4.4.16, netty 4.1.136.Final), so if NVD ever re-broadens either CPE the CVSS >= 7.0 gate fails and forces a fresh triage rather than passing silently. The full triage reasoning for both entries is preserved in the suppression file's header comment. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Up to standards ✅🟢 Issues
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #237.
The classic-
httpcoreentry (CVE-2026-54428 / CVE-2026-54399) and the netty entry (CVE-2026-56816) no longer suppress anything, so they are removed.Evidence
Comparing the OWASP reports from the
mainbaseline (run 31922110421) and the batched-bump branch (run 31958625438):Suppressed CVEs do appear in these reports under Suppressed Vulnerabilities — the last two rows prove it. Zero occurrences therefore means the CVE is not being flagged at all, not that the suppression is quietly working. NVD has narrowed both CPE ranges since the entries were added.
Why this is safe to reverse
The affected artifacts are still resolved in the dependency tree (
httpcore4.4.16, netty 4.1.136.Final). If NVD ever re-broadens either CPE, the CVSS ≥ 7.0 gate fails and forces a fresh triage rather than passing unnoticed. The full triage reasoning for both entries is preserved in the suppression file's header comment.Three suppressions remain, all expiring 2026-10-10. Matches the 2026-07-07 precedent, where the whole set was removed once it went dead.
Verification
./gradlew build— green.security.ymlrun on this branch is the real test: it runs OWASP with the entries gone. If either CVE is still flagged, that run fails and the entries go back.