CVE-2026-117620

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

GHSA-h93r-r52j-vf7v ↗EUVD-2026-112185 ↗

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.
Jenkins Project Jenkins
ETK-2026-2895Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 03h 31msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h50m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Jenkins core versions through 2.587 and LTS versions through 2.580.1 are affected by a flaw in Manage Old Data handling. A user with Overall/Read can cause administrator-actionable warnings that may lead to changes to existing account information, including passwords; administrator interaction is required.

mitigation

Upgrade Jenkins to a currently supported release newer than 2.587, or an LTS release newer than 2.580.1. Limit Overall/Read access and review Manage Old Data warnings carefully before applying changes.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2895",
  "cve_id": "CVE-2026-117620",
  "display_id": "CVE-2026-117620",
  "ghsa_id": "GHSA-h93r-r52j-vf7v",
  "euvd_id": "EUVD-2026-112185",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Administrator-mediated account overwrite in Jenkins",
  "summary": "Jenkins core versions through 2.587 and LTS versions through 2.580.1 are affected by a flaw in Manage Old Data handling. A user with Overall/Read can cause administrator-actionable warnings that may lead to changes to existing account information, including passwords; administrator interaction is required.",
  "mitigation": "Upgrade Jenkins to a currently supported release newer than 2.587, or an LTS release newer than 2.580.1. Limit Overall/Read access and review Manage Old Data warnings carefully before applying changes.",
  "vendor": "Jenkins Project",
  "product": "Jenkins",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Jenkins",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.488064116666667,
  "t0_at": "2026-10-28T16:48:33.708000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T16:48:33.708000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T16:48:33.708000+00:00",
      "url": "https://github.com/advisories/GHSA-h93r-r52j-vf7v"
    }
  }
}

published 2026-10-28 19:13Z
last change 2026-10-29 18:04Z

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.