[GHSA-66cv-5wq4-p78m] Add finder credit and affected package range (CVE-2026-81829) - #9648
Conversation
|
Thanks! Aside from the credit, would the curation team be able to consider this advisory for review (i.e., upgrade it from the NVD mirror entry to a reviewed advisory)? Note that a repository security advisory for this vulnerability already exists in smallrye/smallrye-jwt (GHSA-7x9g-wc63-whmg, published by the maintainer), and this database entry affects Maven ecosystem packages (io.smallrye:smallrye-jwt, quarkus-smallrye-jwt). Happy to help with any additional information to make the review possible. |
|
Updating this PR with the affected package range so the advisory can be considered for review. All versions verified against upstream sources: Affected package: Affected range:
Also added WEB references for the fix PR and the patched release. These coordinates should align this entry with repository security advisory GHSA-7x9g-wc63-whmg for the same CVE. |
839355b to
e3ebfce
Compare
Adds a
creditsentry crediting Sandipan Roy (@ByteHackr) asFINDER, and fills in the emptyaffectedfield with a verified Maven package range, plus supporting references.1. Finder credit
Public evidence supporting this credit:
creatorfield: "Sandipan Roy", accountsaroy)The
creditsstructure follows the OSV schema and the convention already used in this repository (e.g. merged PR #7190).2. Affected package range
affectedwas empty; populated withio.smallrye:smallrye-jwt(Maven), range>= 4.3.0, < 4.6.4— all versions verified against upstream sources:io.smallrye.jwt.auth.principal.AwsAlbKeyResolverwas added by Support AWS ALB token verification smallrye/smallrye-jwt#707 (merged 2023-07-04); release 4.3.0 published 2023-07-05. Verified: class present at tag4.3.0, absent at tag4.2.1.SAFE_KIDregex validation) merged 2026-09-17T14:30Z; release 4.6.4 published 2026-09-17T14:48Z (18 minutes later). Class present unfixed at tag4.6.3.These coordinates align this entry with repository security advisory GHSA-7x9g-wc63-whmg for the same CVE.
Per CONTRIBUTING.md this PR touches exactly one advisory. Happy to adjust the range or details as the curation team sees fit — and if appropriate, would this advisory be a candidate for review given the package mapping and existing RSA for the same CVE? Thanks!