Skip to main content
VulnerabilityPublished

CVE-2026-130235: Okta .NET SDK Abstractions Library · Server-Side Request Forgery (SSRF)

Affects Okta .NET SDK Abstractions LibrarySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 4.0.8 soon.

Data as of 19 Nov 2026, 21:34 UTC

CVSS 3.1 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Okta)CVSS 3.18.7
Patch
Available – fixed in 4.0.8
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade Okta .NET SDK Abstractions Library to 4.0.8.

Affected software

ProductAffectedFixed in
OktaOkta .NET SDK Abstractions LibraryAffected
  • >=1.0.0 <4.0.8
Fixed in
  • 4.0.8

AI-suggested

Upgrade the Okta .NET SDK Abstractions library to version 4.0.8 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated by the vendor advisory.

Description

CVE-2026-130235 is a Server-Side Request Forgery (SSRF) vulnerability in the Okta .NET SDK Abstractions library. The vulnerability allows outbound HTTP requests to be sent to external hosts outside the configured Okta organization domain when processing certain URL formats. This can lead to the transmission of the configured SSWS API token to unintended external destinations. The issue affects versions from 1.0.0 up to, but not including, 4.0.8. A fix is available in version 4.0.8.

References

Community reviews

Loading reviews…