CVE-2026-79957

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

GHSA-5323-vmxx-hx7x ↗EUVD-2026-101517 ↗

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.
servicenext SerTec 1.00
ETK-2026-1769Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 05h 13msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+66h43m
0
+2h
+4h
+6h
+8h
+10h

description

ServiceNext SerTec exposes an authorization flaw in its user-profile API. An authenticated user may obtain other users' profile records by changing the requested account identifier, potentially exposing plaintext passwords and enabling account compromise.

mitigation

Restrict or disable access to the affected user-profile API until server-side ownership checks are enforced, and ensure responses never include passwords. Reset potentially exposed passwords and investigate access logs; no fixed release 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.
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.27%17th percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 18:01Z
Δ 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: an exploit technique exists, 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-14 18:01Z
    ghsa: trigger signal, started the run
  2. 2026-10-14 18:01Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1769",
  "cve_id": "CVE-2026-79957",
  "display_id": "CVE-2026-79957",
  "ghsa_id": "GHSA-5323-vmxx-hx7x",
  "euvd_id": "EUVD-2026-101517",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Insecure direct object reference in ServiceNext SerTec",
  "summary": "ServiceNext SerTec exposes an authorization flaw in its user-profile API. An authenticated user may obtain other users' profile records by changing the requested account identifier, potentially exposing plaintext passwords and enabling account compromise.",
  "mitigation": "Restrict or disable access to the affected user-profile API until server-side ownership checks are enforced, and ensure responses never include passwords. Reset potentially exposed passwords and investigate access logs; no fixed release is recorded.",
  "vendor": "servicenext",
  "product": "SerTec",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.00"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "SerTec",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0027,
  "epss_percentile": 0.1739,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.578092333333334,
  "t0_at": "2026-10-14T18:01:51.493000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T18:01:51.493000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T18:01:51.493000+00:00",
      "url": "https://github.com/advisories/GHSA-5323-vmxx-hx7x"
    }
  }
}

published 2026-10-16 11:28Z
last change 2026-10-21 05:31Z

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.