Skip to content

Record CNA rejection of CVE-2026-97058 for GHSA-hp3w-g68c-fv3c - #10497

Merged
advisory-database[bot] merged 1 commit into
github:BlackishGreen33/advisory-improvement-10497from
BlackishGreen33:bg/security/ghsa-hp3w-cve-status
Oct 22, 2026
Merged

advisory-database[bot] merged 1 commit into
github:BlackishGreen33/advisory-improvement-10497from
BlackishGreen33:bg/security/ghsa-hp3w-cve-status

Conversation

@BlackishGreen33

Copy link
Copy Markdown

Summary

Add the official CNA rejection status and a primary-source reference to GHSA-hp3w-g68c-fv3c. Please review whether this GitHub advisory should also be withdrawn.

CVE-2026-97058: REJECTED (2026-10-12)
GHSA-hp3w-g68c-fv3c: no withdrawal recorded

The official CVE record has state: REJECTED and dateRejected: 2026-10-12T19:33:32.335Z. The CNA gives only the generic rejected/withdrawn reason, with no technical explanation. The upstream discussion also notes the rejection.

This proposal records that public status without assuming that CVE rejection automatically invalidates an independent GHSA. It leaves withdrawn, affected versions, severity, and the existing technical description unchanged for the curation team's assessment. It does not claim a patched sprintf-js release exists.

Evidence

  • Before: the advisory omits the October 12 CNA rejection and has no reference to the official rejected record.
  • After: the CVE status is documented and linked to an immutable CVEProject commit; technical and affected-version fields remain unchanged.
  • JSON and OSV schema validation passed; only this advisory is changed.

Merge Danger

Door: two-way

Blast Radius: metadata

No package code, affected ranges, or severity changes. Withdrawal remains a curation decision.

Copilot AI max review requested due to automatic review settings October 22, 2026 15:59

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@github-actions
github-actions Bot changed the base branch from main to BlackishGreen33/advisory-improvement-10497 October 22, 2026 16:07
@G-Rath

G-Rath commented Oct 22, 2026 •

Copy link
Copy Markdown

The advisory should be withdrawn.

I have forwarded GitHub a copy of my dispute that I made to VulnCheck and MITRE (after the former failed to respond in the required time per the CNA obligations)

@advisory-database
advisory-database Bot merged commit 93a9832 into github:BlackishGreen33/advisory-improvement-10497 Oct 22, 2026
2 checks passed
@advisory-database

Copy link
Copy Markdown
Contributor

Hi @BlackishGreen33! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!

@G-Rath

G-Rath commented Oct 22, 2026

Copy link
Copy Markdown

While this says it was merged, what happened in actuality was the advisory was withdrawn by GH 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants