Boruta accepts expired JWT client assertions due to missing exp claim validation
Authentication Bypass by Capture-replay vulnerability in malach-it Boruta allows an attacker who has obtained a previously valid JWT client assertion to authenticate as the issuing OAuth client after the assertion has expired. Boruta accepts JWT-based client authentication (client_secret_jwt and private_key_jwt token endpoint authentication methods) but never enforces that the assertion's exp claim is in the future. The pre-check helper Boruta.Oauth.Request.Base.check_expiration/1 in lib/boruta/oauth/request/base.ex only verifies that an exp claim is present (it pattern-matches on the existence of the key and returns success), and the Joken token configuration used for signature verification, Boruta.Oauth.Authorization.Client.Token.token_config/0 in lib/boruta/oauth/authorization/client.ex, returns an empty map, so Joken's default exp claim validator is not engaged either. Any attacker who obtains a validly-signed client assertion (for example through logs, reverse proxies, browser tooling, or other observability surfaces) can replay it indefinitely to authenticate as the client and obtain access tokens with that client's privileges. This issue affects boruta: from 2.3.0 before 2.3.7.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-53431
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 04:12 UTC · Revision 1
Source evidence
Boruta accepts expired JWT client assertions due to missing exp claim validation
core-osv · Original sourcePublished 30 Jul 2026, 14:17 UTC
Authentication Bypass by Capture-replay vulnerability in malach-it Boruta allows an attacker who has obtained a previously valid JWT client assertion to authenticate as the issuing OAuth client after the assertion has expired. Boruta accepts JWT-based client authentication (client_secret_jwt and private_key_jwt token endpoint authentication methods) but never enforces that the assertion's exp claim is in the future. The pre-check helper Boruta.Oauth.Request.Base.check_expiration/1 in lib/boruta/oauth/request/base.ex only verifies that an exp claim is present (it pattern-matches on the existence of the key and returns success), and the Joken token configuration used for signature verification, Boruta.Oauth.Authorization.Client.Token.token_config/0 in lib/boruta/oauth/authorization/client.ex, returns an empty map, so Joken's default exp claim validator is not engaged either. Any attacker who obtains a validly-signed client assertion (for example through logs, reverse proxies, browser tooling, or other observability surfaces) can replay it indefinitely to authenticate as the client and obtain access tokens with that client's privileges. This issue affects boruta: from 2.3.0 before 2.3.7.
osv:CVE-2026-53431
Complete source record
{
"id": "f7a97e601901d1e988b2f2a57a4bdd0da48c6eaf9c8e086bbaabb40a4c212c16",
"url": "https://osv.dev/vulnerability/CVE-2026-53431",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Boruta accepts expired JWT client assertions due to missing exp claim validation",
"summary": "Authentication Bypass by Capture-replay vulnerability in malach-it Boruta allows an attacker who has obtained a previously valid JWT client assertion to authenticate as the issuing OAuth client after the assertion has expired. Boruta accepts JWT-based client authentication (client_secret_jwt and private_key_jwt token endpoint authentication methods) but never enforces that the assertion's exp claim is in the future. The pre-check helper Boruta.Oauth.Request.Base.check_expiration/1 in lib/boruta/oauth/request/base.ex only verifies that an exp claim is present (it pattern-matches on the existence of the key and returns success), and the Joken token configuration used for signature verification, Boruta.Oauth.Authorization.Client.Token.token_config/0 in lib/boruta/oauth/authorization/client.ex, returns an empty map, so Joken's default exp claim validator is not engaged either. Any attacker who obtains a validly-signed client assertion (for example through logs, reverse proxies, browser tooling, or other observability surfaces) can replay it indefinitely to authenticate as the client and obtain access tokens with that client's privileges. This issue affects boruta: from 2.3.0 before 2.3.7.",
"evidence": "osv:CVE-2026-53431",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2026-53431",
"aliases": [
"CVE-2026-53431",
"EEF-CVE-2026-53431",
"GHSA-xjv8-vmh5-xhf6"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/malach-it/boruta_auth",
"type": "GIT",
"events": [
{
"introduced": "5bfbe1c5443bffe71cf1bf954bbdff61327d9a83"
},
{
"fixed": "5204f88f9b2cdd9637a755337ed5f99185be5474"
},
{
"introduced": "0"
},
{
"fixed": "fa474710cfc57abf0ab1374c615cc66df1a05239"
},
{
"fixed": "69363432aa36760fc5438e4e17115d0f7c1b925a"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "5bfbe1c5443bffe71cf1bf954bbdff61327d9a83"
},
{
"fixed": "5204f88f9b2cdd9637a755337ed5f99185be5474"
}
],
"source": "AFFECTED_FIELD",
"strategy": "ChangesAt"
},
{
"range": [
{
"introduced": "2.3.0"
},
{
"fixed": "2.3.7"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "5204f88f9b2cdd9637a755337ed5f99185be5474"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "69363432aa36760fc5438e4e17115d0f7c1b925a"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"2.3.6",
"2.3.5",
"3.0.0-beta.4",
"2.3.4",
"3.0.0-beta.3",
"3.0.0-beta.2",
"3.0.0-beta.1",
"2.3.2"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53431.json"
}
}
],
"modified": "2026-10-28T02:30:49.440257163Z",
"provider": "osv",
"references": [
"https://cna.erlef.org/cves/CVE-2026-53431.html",
"https://github.com",
"https://osv.dev/vulnerability/EEF-CVE-2026-53431",
"https://repo.hex.pm",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53431.json",
"https://github.com/malach-it/boruta_auth/security/advisories/GHSA-xjv8-vmh5-xhf6",
"https://nvd.nist.gov/vuln/detail/CVE-2026-53431",
"https://github.com/malach-it/boruta_auth/commit/5204f88f9b2cdd9637a755337ed5f99185be5474",
"https://github.com/malach-it/boruta_auth/commit/69363432aa36760fc5438e4e17115d0f7c1b925a",
"https://github.com/malach-it/boruta_auth"
],
"provider_metadata": {
"cwe_ids": [
"CWE-294"
],
"cna_assigner": "EEF",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53431.json"
}
},
"related_cves": [
{
"value": "CVE-2026-53431",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 518037,
"published_at": "2026-07-30T14:17:27.909+00:00"
}