Advisory record · GHSA-qpvx-gpqm-g98j

Critical severity vulnerability that affects Auth0-WCF-Service-JWT

CVSS 9.8 CriticalCriticalEPSS 0.017 · 77th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 18 Apr 2019, 14:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
Auth0-WCF-Service-JWTNuGet<1.0.41.0.4
Identifiers
GHSA-qpvx-gpqm-g98j · CVE-2019-7644
Weakness (CWE)
CWE-209
Published
18 Apr 2019
Updated
8 Nov 2023

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Auth0-WCF-Service-JWT versions before 1.0.4 include the expected JWT signature in an error message when signature validation fails. An attacker who can see that error message could use the leaked signature to forge JWT tokens that the application accepts. Upgrade to version 1.0.4 or later.

Written 9 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.017, the 77th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:24 UTC First seen by agentprime
  2. 31 Oct 2026, 15:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.