CVE-2026-123010

waiting for further signalsZero needs more public information before it can validate it.

GHSA-cc92-p629-wm8f ↗EUVD-2026-117323 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
twilio-labs netlify-okta-auth <= 1.0.2
CWE-669 Incorrect Resource Transfer Between Spheres
ETK-2026-3580Zero's internal tracking ID, independent of the CVE number., permanent identifier
17h 46msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h49m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

netlify-okta-auth through 1.0.2 does not verify the issuer claim when handling tokens. This can affect the outbound request used to obtain a public signing key, with further impact possible when oktaUrl is not configured.

mitigation

Configure oktaUrl explicitly and restrict outbound HTTP access to approved identity-provider endpoints. Monitor for a corrected release, as no fixed version is recorded.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 04:10Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-05 04:10Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-123010

{
  "etk_id": "ETK-2026-3580",
  "cve_id": "CVE-2026-123010",
  "display_id": "CVE-2026-123010",
  "ghsa_id": "GHSA-cc92-p629-wm8f",
  "euvd_id": "EUVD-2026-117323",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Issuer validation flaw in netlify-okta-auth",
  "summary": "netlify-okta-auth through 1.0.2 does not verify the issuer claim when handling tokens. This can affect the outbound request used to obtain a public signing key, with further impact possible when oktaUrl is not configured.",
  "mitigation": "Configure oktaUrl explicitly and restrict outbound HTTP access to approved identity-provider endpoints. Monitor for a corrected release, as no fixed version is recorded.",
  "vendor": "twilio-labs",
  "product": "netlify-okta-auth",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "netlify-okta-auth",
      "purl": null
    }
  ],
  "cwes": [
    669
  ],
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.3465597,
  "t0_at": "2026-11-05T04:10:37.414000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T04:10:37.414000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T04:10:37.414000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123010"
    }
  }
}

published 2026-11-05 04:40Z
last change 2026-11-05 11:44Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.