CVE-2026-76143

validatedZero produced an exploit or a check.

GHSA-83p8-vgfm-3hhr ↗EUVD-2026-90485 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Genians, Inc Genian SSL PNS (frodo-core) < 5.0.0
fixed in 5.0.0
CWE-862 Missing Authorization
ETK-2026-218, permanent identifier
+3h17mTTV
8mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+3h17magent stopped
0
+1h
+2h
+3h

description

Affected frodo-core versions in Genian SSL PNS may permit an attacker to circumvent multi-factor authentication during login. Exploitation requires the attacker to be able to alter a login request parameter.

mitigation

Upgrade frodo-core to version 5.0.0 or later.

fixed in 5.0.0

check
available
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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%22nd percentile
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 04:53Z
Δ 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

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-01 04:53Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-218",
  "cve_id": "CVE-2026-76143",
  "display_id": "CVE-2026-76143",
  "ghsa_id": "GHSA-83p8-vgfm-3hhr",
  "euvd_id": "EUVD-2026-90485",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization MFA bypass in frodo-core",
  "summary": "Affected frodo-core versions in Genian SSL PNS may permit an attacker to circumvent multi-factor authentication during login. Exploitation requires the attacker to be able to alter a login request parameter.",
  "mitigation": "Upgrade frodo-core to version 5.0.0 or later.",
  "vendor": "Genians, Inc",
  "product": "Genian SSL PNS (frodo-core)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 5.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5.0.0"
      ],
      "package_name": "frodo-core",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H",
  "epss_score": 0.0031,
  "epss_percentile": 0.2259,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 8.45220095,
  "t0_at": "2026-10-01T04:53:36.564000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-01T08:10:29.395198+00:00",
      "days": 0.1367225833101852,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T04:53:36.564000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-01T04:53:36.564000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T04:53:36.564000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76143"
    }
  }
}

published 2026-10-01 07:42Z
last change 2026-10-21 09:43Z

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.