CVE-2026-112305

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

GHSA-6cr7-7xqc-c37c ↗EUVD-2026-104397 ↗

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.
semaphoreui Semaphore UI <= 2.19.16
ETK-2026-2080Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 21h 53msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h32m
0
+2h
+6h
+8h
+10h
+12h

description

Semaphore UI through 2.19.16 allows task environment input to override protected Ansible variables. An authenticated user with the task_runner role may cause commands to run as the Semaphore server user, potentially exposing server-held keys and secrets.

mitigation

Remove or tightly limit the task_runner role until an updated Semaphore UI release is available and deployed. Restrict access to the Semaphore service and protect credentials accessible to its server account.

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.56%45th percentile
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 15:28Z
Δ 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-19 15:28Z
    ghsa: trigger signal, started the run
  2. 2026-10-19 15:28Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2080",
  "cve_id": "CVE-2026-112305",
  "display_id": "CVE-2026-112305",
  "ghsa_id": "GHSA-6cr7-7xqc-c37c",
  "euvd_id": "EUVD-2026-104397",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Task environment variable injection in Semaphore UI",
  "summary": "Semaphore UI through 2.19.16 allows task environment input to override protected Ansible variables. An authenticated user with the task_runner role may cause commands to run as the Semaphore server user, potentially exposing server-held keys and secrets.",
  "mitigation": "Remove or tightly limit the task_runner role until an updated Semaphore UI release is available and deployed. Restrict access to the Semaphore service and protect credentials accessible to its server account.",
  "vendor": "semaphoreui",
  "product": "Semaphore UI",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.19.16"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Semaphore UI",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0056,
  "epss_percentile": 0.4576,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 37.39127345,
  "t0_at": "2026-10-19T15:28:55.694000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T15:28:55.694000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T15:28:55.694000+00:00",
      "url": "https://github.com/advisories/GHSA-6cr7-7xqc-c37c"
    }
  }
}

published 2026-10-19 19:23Z
last change 2026-10-21 15:37Z

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.