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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 15:09 UTC First seen by agentprime
- 31 Oct 2026, 15:09 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-5pq9-5mpr-jj85
- OSV: GHSA-5pq9-5mpr-jj85
- github.com/samrocketman/jervis/security/advisories/GHSA-5pq9-5mpr-jj85
- nvd.nist.gov/vuln/detail/CVE-2025-68925
- github.com/samrocketman/jervis/commit/c3981ff71de7b0f767dfe7b37a2372cb2a51974a
- github.com/samrocketman/jervis
- github.com/samrocketman/jervis/blob/157d2b63ffa5c4bb1d8ee2254950fd2231de2b05/src/main/groovy/net/gleske/jervis/tools/SecurityIO.groovy#L244-L249
- github.com/samrocketman/jervis/commit/c3981ff71de7b0f767dfe7b37a2372cb2a51974a