Libokhttp java: OkHttp through 5.5.1 contains an improper certificate validation vulnerability in CertificatePinner
Affects libokhttp-javaSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium.
Data as of 18 Nov 2026, 15:36 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.8 |
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10libokhttp-javapkg:deb/ubuntu/libokhttp-java?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlibokhttp-javapkg:deb/ubuntu/libokhttp-java?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlibokhttp-javapkg:deb/ubuntu/libokhttp-java?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlibokhttp-javapkg:deb/ubuntu/libokhttp-java?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSlibokhttp-javapkg:deb/ubuntu/libokhttp-java?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSlibokhttp-javapkg:deb/ubuntu/libokhttp-java?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, avoid using trailing-dot hostnames in pinned hosts or implement additional hostname normalization in the application if possible.
Description
OkHttp versions through 5.5.1 have an improper certificate validation vulnerability in the CertificatePinner component. The flaw occurs because Pin.matchesHostname does not normalize trailing-dot hostnames, causing the pin checks to be skipped. This allows network attackers with a CA-trusted certificate that does not match the configured pins to intercept or modify TLS traffic when applications request the trailing-dot form of pinned hosts.
References
- ubuntu.com/security/CVE-2026-129482 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-129482 (opens in a new tab)
- github.com/lysine-dev/okhttp/issues/9724 (opens in a new tab)
- github.com/lysine-dev/okhttp/pull/9734 (opens in a new tab)
- github.com/lysine-dev/okhttp/commit/30aa589761a9b4f5fe84c00e21e5ab44b22bd7c1 (opens in a new tab)
- github.com/lysine-dev/okhttp/blob/parent-5.5.1/okhttp/src/commonJvmAndroid/kotlin/okhttp3/CertificatePinner.kt (opens in a new tab)
- vulncheck.com/advisories/okhttp-through-5.5.1-certificate-pinning-bypass-via-trailing-dot-hostname (opens in a new tab)