Skip to content

Conversation

@jcburgo
Copy link

@jcburgo jcburgo commented Dec 10, 2025

Adding CVE-2025-55182 to GHSA-9qr9-h5gf-34mp to reflect NVD data.

@github-actions github-actions bot changed the base branch from main to jcburgo/advisory-improvement-6535 December 10, 2025 20:13
@shelbyc
Copy link
Contributor

shelbyc commented Dec 11, 2025

Hi @jcburgo, I can't connect CVE-2025-55182 to GHSA-9qr9-h5gf-34mp because that CVE ID is already attached to GHSA-fv66-9v8q-g76r, but I'm going to try adding GHSA-fv66-9v8q-g76r and GHSA-fmh4-wr37-44fp as reference links to see if that facilitates better connections between the advisories that share a CVE.

@advisory-database advisory-database bot merged commit 57665cb into github:jcburgo/advisory-improvement-6535 Dec 11, 2025
2 checks passed
@advisory-database
Copy link
Contributor

Hi @jcburgo! 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!

@jcburgo
Copy link
Author

jcburgo commented Dec 12, 2025

I noticed that GHSA-fmh4-wr37-44fp and GHSA-fv66-9v8q-g76r have the CVE ID on the advisory page set to CVE-2025-55182, but GHSA-9qr9-h5gf-34mp has CVE ID set to “No known CVE”. Can we update GHSA-9qr9-h5gf-34mp to list CVE-2025-55182. Maybe by adding this to it?:

    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-55182"
    },

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.

2 participants