Advisory record · GHSA-5pq9-5mpr-jj85

Jervis Has a JWT Algorithm Confusion Vulnerability

CVSS 6.9 MediumEPSS 0.0015 · 4th percentile

Published by the GitHub Advisory Database at 13 Jan 2026, 14:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
net.gleske:jervisMaven<2.22.2
Identifiers
GHSA-5pq9-5mpr-jj85 · CVE-2025-68925
Weakness (CWE)
CWE-347
Published
13 Jan 2026
Updated
3 Feb 2026

Machine-written summary

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

Jervis (net.gleske:jervis, Maven) versions before 2.2 do not check that a JWT header specifies RS256 as its algorithm. The advisory says this could allow JWT forgery, depending on how the wider system uses the tokens. Upgrade to Jervis 2.2, which verifies the algorithm and JWT structure.

Written 7 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
6.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0015, the 4th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:09 UTC First seen by agentprime
  2. 31 Oct 2026, 15:09 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.