CVE-2026-76142

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

GHSA-8pg5-29m6-59f2 ↗EUVD-2026-90484 ↗

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.
Genians, Inc Genian NAC 5.0.75 LTS Release >= 5.0.75 LTS(Revision 135823); >= 5.0.85(Revision 147181); >= 5.0.86(Revision 148018); >= 6.0.35(Revision 135814); >= 6.0.45(Revision 147169); >= 6.0.46(Revision 148028)
fixed in 5.0.75 LTS(Revision 148667), 5.0.85(Revision 148666), 5.0.86(Revision 148665), 6.0.35(Revision 148672), 6.0.45(Revision 148671), 6.0.46(Revision 148670)
CWE-284 Improper Access Control
ETK-2026-208, permanent identifier
20d 04h 15msince last run
1h 12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h51m
0
+4h
+6h
+8h
+10h
+12h

description

Genian NAC and Genian ZTNA policy servers are affected by inadequate authentication and authorization on an internal IPC SOAP interface. An unauthenticated attacker able to reach that endpoint can invoke internal server functions.

mitigation

Upgrade to the fixed build for the deployed release line: NAC 5.0.75 LTS build 148667, 5.0.85 Stable build 148666, 5.0.86 build 148665; or ZTNA 6.0.35 LTS build 148672, 6.0.45 Stable build 148671, or 6.0.46 build 148670. Restrict network access to the internal IPC SOAP endpoint until upgrades are complete.

fixed in 5.0.75 LTS(Revision 148667), 5.0.85(Revision 148666), 5.0.86(Revision 148665), 6.0.35(Revision 148672), 6.0.45(Revision 148671), 6.0.46(Revision 148670)

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.
0.33%25th percentile
agent run time
1h 12m
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

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-10-01 04:53Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-208",
  "cve_id": "CVE-2026-76142",
  "display_id": "CVE-2026-76142",
  "ghsa_id": "GHSA-8pg5-29m6-59f2",
  "euvd_id": "EUVD-2026-90484",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated IPC SOAP access control flaw in Genian NAC/ZTNA",
  "summary": "Genian NAC and Genian ZTNA policy servers are affected by inadequate authentication and authorization on an internal IPC SOAP interface. An unauthenticated attacker able to reach that endpoint can invoke internal server functions.",
  "mitigation": "Upgrade to the fixed build for the deployed release line: NAC 5.0.75 LTS build 148667, 5.0.85 Stable build 148666, 5.0.86 build 148665; or ZTNA 6.0.35 LTS build 148672, 6.0.45 Stable build 148671, or 6.0.46 build 148670. Restrict network access to the internal IPC SOAP endpoint until upgrades are complete.",
  "vendor": "Genians, Inc",
  "product": "Genian NAC 5.0.75 LTS Release",
  "affected": [
    {
      "affected_notes": [
        ">= 5.0.75 LTS(Revision 135823)"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "5.0.75 LTS(Revision 148667)"
      ],
      "package_name": "Genian NAC V5.0",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 5.0.85(Revision 147181)"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "5.0.85(Revision 148666)"
      ],
      "package_name": "Genian NAC V5.0",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 5.0.86(Revision 148018)"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "5.0.86(Revision 148665)"
      ],
      "package_name": "Genian NAC V5.0",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 6.0.35(Revision 135814)"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "6.0.35(Revision 148672)"
      ],
      "package_name": "Genian ZTNA V6.0",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 6.0.45(Revision 147169)"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "6.0.45(Revision 148671)"
      ],
      "package_name": "Genian ZTNA V6.0",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 6.0.46(Revision 148028)"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "6.0.46(Revision 148670)"
      ],
      "package_name": "Genian ZTNA V6.0",
      "purl": null
    }
  ],
  "cwes": [
    284
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H",
  "epss_score": 0.0033,
  "epss_percentile": 0.2509,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 71.61849403333333,
  "t0_at": "2026-10-01T04:53:35.730000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T04:53:35.730000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T04:53:35.730000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76142"
    }
  }
}

published 2026-10-01 05:33Z
last change 2026-10-21 10:15Z

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.