CVE-2025-68925Network attack vector

JWT forgery via unchecked algorithm header

Published Jan 13, 2026 · Updated Jan 13, 2026

JWT algorithm confusion in Jervis before 2.2 allows remote attackers to forge tokens by supplying a non-RS256 JWT header. SecurityIO.verifyJsonWebToken tokenizes the input and calls RS256 signature verification without parsing the protected header or requiring its alg value to be RS256. The method is intended for GitHub JWTs, so token forgery affects external systems only when their callers rely on this verifier; the documented impact is integrity only.

CVSS severity6.9
Medium
EPSS probability0.15%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

JWT algorithm confusion in Jervis before 2.2 allows remote attackers to forge tokens by supplying a non-RS256 JWT header. SecurityIO.verifyJsonWebToken tokenizes the input and calls RS256 signature verification without parsing the protected header or requiring its alg value to be RS256. The method is intended for GitHub JWTs, so token forgery affects external systems only when their callers rely on this verifier; the documented impact is integrity only.

The record

CVE
CVE-2025-68925
Published
Jan 13, 2026
Updated
Jan 13, 2026
Vendor
Sam Gleske
Product
Jervis
Classifications
CWE-347, T1550.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 13, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 13, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Sam Gleske · Jervisversion=< 2.2

Published CVSS scores

5.3NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
6.9GitHub, Inc.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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1550.001Application Access Token

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo