VulnerabilityPublished 2 Jul 2026Updated 8 Nov 2026

CVE-2026-59096: dapr · Origin Validation Error

Affects daprSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 8 Nov 2026, 14:35 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 3.1	7.5
CNA (VulnCheck)	CVSS 4.0	8.2

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers can reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-07-06.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jul 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 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
daprdapr	Affected =1.17.0 =1.18.0	Fixed in–
GitHubdapr`pkg:github/dapr`Other threats	Affected =1.17.0 =1.18.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the vulnerability requires the OIDC server to be enabled without configured jwt-issuer or oidc-allowed-hosts, administrators should configure a strict allowed-hosts list or specify a jwt-issuer to prevent exploitation. Monitor vendor advisories for official patches or updates. Until a fix is available, avoid enabling the OIDC server without proper configuration of issuer and allowed hosts.

Description

CVE-2026-59096 is a high-severity vulnerability in dapr versions 1.17.0 and 1.18.0 involving an origin validation error in Dapr Sentry's OIDC discovery endpoint. The endpoint derives issuer and jwks_uri values from the request Host header, trusting an attacker-controlled X-Forwarded-Host header without validation when no allowed-hosts list is configured (the default). This allows a remote unauthenticated attacker to poison the discovery document, causing relying parties to fetch JSON Web Key Sets (JWKS) from an attacker-controlled server and accept attacker-signed JWTs. Exploitation requires the OIDC server to be enabled without a configured jwt-issuer or oidc-allowed-hosts.

Impact

An unauthenticated remote attacker can exploit this vulnerability to poison the OIDC discovery document, causing relying parties to accept attacker-signed JWTs. This compromises the integrity of authentication and authorization processes relying on these tokens, potentially leading to unauthorized access or privilege escalation. The vulnerability does not impact confidentiality or availability directly but has a high impact on integrity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Nov 2026, 14:35 UTC

Technical details

References

Community reviews

Related threats