CVE-2026-61791

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

EUVD-2026-108209 ↗

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.
schorschii OCO-Server <= 1.2.0
fixed in 1.2.1
CWE-83 Improper Neutralization of Script in Attributes in a Web Page
ETK-2026-2481Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 39msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h45m
0
+2h
+6h
+8h
+10h
+12h

description

OCO-Server versions before 1.2.1 can render a stored computer hostname in a way that executes script when an administrator uses an affected command button. An attacker needs the shared agent registration key and enabled agent self-registration to submit the hostname; successful execution occurs in the administrator's session.

mitigation

Upgrade OCO-Server to version 1.2.1. Until upgraded, disable agent self-registration and protect or rotate the shared agent registration key.

fixed in 1.2.1

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 14:55Z
Δ 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-22 14:55Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2481",
  "cve_id": "CVE-2026-61791",
  "display_id": "CVE-2026-61791",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-108209",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in OCO-Server hostnames",
  "summary": "OCO-Server versions before 1.2.1 can render a stored computer hostname in a way that executes script when an administrator uses an affected command button. An attacker needs the shared agent registration key and enabled agent self-registration to submit the hostname; successful execution occurs in the administrator's session.",
  "mitigation": "Upgrade OCO-Server to version 1.2.1. Until upgraded, disable agent self-registration and protect or rotate the shared agent registration key.",
  "vendor": "schorschii",
  "product": "OCO-Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.2.1"
      ],
      "package_name": "schorschii/OCO-Server",
      "purl": null
    }
  ],
  "cwes": [
    83
  ],
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.06545925,
  "t0_at": "2026-10-22T14:55:54.269000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T14:55:54.269000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T14:55:54.269000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-61791"
    }
  }
}

published 2026-10-22 18:26Z
last change 2026-10-22 19:01Z

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.