Authentication bypass via unescaped JWT tag claim
Published Feb 25, 2026 · Updated Feb 25, 2026
SQL injection in OpenSIPS 3.1 through 3.6.3 allows remote attackers to bypass JWT authentication and impersonate identities. jwt_db_authorize() decodes an unverified JWT tag claim and interpolates it unescaped into a raw query whose returned secret is then trusted for signature verification. Exploitation requires auth_jwt with db_mode enabled and a SQL backend; a crafted token can inject a known signing secret and authenticate as an arbitrary mapped identity.
Summary
What happened
SQL injection in OpenSIPS 3.1 through 3.6.3 allows remote attackers to bypass JWT authentication and impersonate identities. jwt_db_authorize() decodes an unverified JWT tag claim and interpolates it unescaped into a raw query whose returned secret is then trusted for signature verification. Exploitation requires auth_jwt with db_mode enabled and a SQL backend; a crafted token can inject a known signing secret and authenticate as an arbitrary mapped identity.
The record
- CVE
- CVE-2026-25554
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- OpenSIPS
- Product
- OpenSIPS
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 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.
- Affected versionversion=3.1 <3.6.4
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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