CVE-2025-27144: Go JOSE's Parsing Vulnerable to Denial of Service
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: azl3 cert-manager 1.12.15-2 on Azure Linux 3.0 1.12.15-2; azl3 cert-manager 1.12.15-3 on Azure Linux 3.0 1.12.15-2; azl3 containerd 1.7.13-7 on Azure Linux 3.0 1.7.13-7.
Low priority for now. Upgrade to azl3 cert-manager 1.12.15-2 on Azure Linux 3.0 1.12.15-2; azl3 cert-manager 1.12.15-3 on Azure Linux 3.0 1.12.15-2; azl3 containerd 1.7.13-7 on Azure Linux 3.0 1.7.13-7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.
- BDU:2025-08606
- GHSA-c6gw-w398-hv78
- ALSA-2025:19566
- ALSA-2025:7389
- ALSA-2025:7397
- ALSA-2025:7459
- ALSA-2025:7462
- ALSA-2025:7467
- GO-2025-3485
- openSUSE-SU-2025:0080-1
- openSUSE-SU-2025:14839-1
- openSUSE-SU-2025:14840-1
- openSUSE-SU-2025:14865-1
- openSUSE-SU-2025:14871-1
- openSUSE-SU-2025:14909-1
- openSUSE-SU-2025:14988-1
- openSUSE-SU-2025:14990-1
- openSUSE-SU-2025:15158-1
- openSUSE-SU-2025:15304-1
- openSUSE-SU-2025:15305-1
- Published
- Feb 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 34th percentile
- CWE
- CWE-770
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
go-jose go-jose
- >= 4.0.0, < 4.0.5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | buildah | before 2:1.39.4-1.el10_0 | 2:1.39.4-1.el10_0 |
| AlmaLinux:10 | buildah-tests | before 2:1.39.4-1.el10_0 | 2:1.39.4-1.el10_0 |
| AlmaLinux:10 | osbuild-composer | before 134.1-3.el10_0.alma.1 | 134.1-3.el10_0.alma.1 |
| AlmaLinux:10 | osbuild-composer-core | before 134.1-3.el10_0.alma.1 | 134.1-3.el10_0.alma.1 |
| AlmaLinux:10 | osbuild-composer-worker | before 134.1-3.el10_0.alma.1 | 134.1-3.el10_0.alma.1 |
| AlmaLinux:10 | podman | before 6:5.4.0-9.el10_0 | 6:5.4.0-9.el10_0 |
| AlmaLinux:10 | podman-docker | before 6:5.4.0-9.el10_0 | 6:5.4.0-9.el10_0 |
| AlmaLinux:10 | podman-remote | before 6:5.4.0-9.el10_0 | 6:5.4.0-9.el10_0 |
| AlmaLinux:10 | podman-tests | before 6:5.4.0-9.el10_0 | 6:5.4.0-9.el10_0 |
| AlmaLinux:10 | skopeo | before 2:1.18.1-1.el10_0 | 2:1.18.1-1.el10_0 |
| AlmaLinux:10 | skopeo-tests | before 2:1.18.1-1.el10_0 | 2:1.18.1-1.el10_0 |
| AlmaLinux:9 | buildah | before 2:1.39.4-1.el9_6 | 2:1.39.4-1.el9_6 |
| AlmaLinux:9 | buildah-tests | before 2:1.39.4-1.el9_6 | 2:1.39.4-1.el9_6 |
| AlmaLinux:9 | skopeo | before 2:1.18.1-1.el9_6 | 2:1.18.1-1.el9_6 |
| AlmaLinux:9 | skopeo-tests | before 2:1.18.1-1.el9_6 | 2:1.18.1-1.el9_6 |
| Debian:13 | golang-github-go-jose-go-jose | before 4.0.5-1 | 4.0.5-1 |
| Go | github.com/go-jose/go-jose | from 0 | — |
| Go | github.com/go-jose/go-jose | before 3.0.4 | 3.0.4 |
| Go | github.com/go-jose/go-jose/v3 | before 3.0.4 | 3.0.4 |
| Go | github.com/go-jose/go-jose/v4 | before 4.0.5 | 4.0.5 |
| Go | github.com/square/go-jose | from 0 | — |
| openSUSE:Leap 15.6 | apptainer | before 1.4.5-150600.4.12.1 | 1.4.5-150600.4.12.1 |
| openSUSE:Leap 15.6 | apptainer | before 1.3.6-150600.4.9.1 | 1.3.6-150600.4.9.1 |
| openSUSE:Leap 15.6 | buildah | before 1.35.5-150500.3.31.1 | 1.35.5-150500.3.31.1 |
+96
Same product
go-jose: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-116587Go JOSE: DoS when parsing JWKs that contain RSA keys30Monitor
- CVE-2026-116586Go JOSE: Panics in JSON parsing27Monitor
- CVE-2026-116585Go JOSE: Panic during CBC-HMAC processing27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 cert-manager 1.12.15-2 on Azure Linux 3.0 | 1.12.15-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 cert-manager 1.12.15-3 on Azure Linux 3.0 | 1.12.15-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 containerd 1.7.13-7 on Azure Linux 3.0 | 1.7.13-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 containerd 1.7.13-8 on Azure Linux 3.0 | 1.7.13-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 containerd2 2.0.0-6 on Azure Linux 3.0 | 2.0.0-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 containerd2 2.0.0-9 on Azure Linux 3.0 | 2.0.0-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 containerized-data-importer 1.57.0-13 on Azure Linux 3.0 | 1.57.0-13 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 containerized-data-importer 1.57.0-14 on Azure Linux 3.0 | 1.57.0-13 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 dcos-cli 1.2.0-17 on Azure Linux 3.0 | 1.2.0-17 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 dcos-cli 1.2.0-18 on Azure Linux 3.0 | 1.2.0-17 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 gh 2.62.0-7 on Azure Linux 3.0 | 2.62.0-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 gh 2.62.0-8 on Azure Linux 3.0 | 2.62.0-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 ig 0.37.0-2 on Azure Linux 3.0 | 0.37.0-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 ig 0.37.0-4 on Azure Linux 3.0 | 0.37.0-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 influxdb 2.7.5-2 on Azure Linux 3.0 | 2.7.5-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 influxdb 2.7.5-5 on Azure Linux 3.0 | 2.7.5-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 keda 2.14.1-3 on Azure Linux 3.0 | 2.14.1-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 keda 2.14.1-7 on Azure Linux 3.0 | 2.14.1-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kubernetes 1.30.10-3 on Azure Linux 3.0 | 1.30.10-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kubernetes 1.30.10-7 on Azure Linux 3.0 | 1.30.10-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 moby-containerd-cc 1.7.7-9 on Azure Linux 3.0 | 1.7.7-9 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 packer 1.9.5-6 on Azure Linux 3.0 | 1.9.5-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 packer 1.9.5-9 on Azure Linux 3.0 | 1.9.5-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 skopeo 1.14.4-4 on Azure Linux 3.0 | 1.14.4-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 skopeo 1.14.4-5 on Azure Linux 3.0 | 1.14.4-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 telegraf 1.31.0-10 on Azure Linux 3.0 | 1.31.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 telegraf 1.31.0-8 on Azure Linux 3.0 | 1.31.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 cert-manager 1.11.2-19 on CBL Mariner 2.0 | 1.11.2-19 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 cert-manager 1.11.2-22 on CBL Mariner 2.0 | 1.11.2-19 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 cert-manager 1.11.2-22 on CBL-Mariner 2.0 | 1.11.2-19 · CBL-Mariner Releases | Microsoft (MSRC) |
+90
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.