CVE-2026-106708

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

GHSA-4mh8-j9rq-c7hj ↗EUVD-2026-102426 ↗

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.
XXL-JOB n/a
ETK-2026-1732Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 17h 33msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+48h23m
0
+2h
+4h
+6h
+8h
+10h

description

XXL-JOB versions up to and including 3.5.0-SNAPSHOT have insufficient request-forgery defenses for user-management operations. An attacker may cause account-management changes through a victim's browser if the victim interacts with attacker-controlled content while able to access the affected service.

mitigation

Apply CSRF validation to user-management operations and accept only the intended HTTP methods for state-changing requests. Until a patched release is identified, restrict access to the management interface to trusted users and networks.

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.
0.15%3rd percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 00:00Z
Δ 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-15 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1732",
  "cve_id": "CVE-2026-106708",
  "display_id": "CVE-2026-106708",
  "ghsa_id": "GHSA-4mh8-j9rq-c7hj",
  "euvd_id": "EUVD-2026-102426",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CSRF in XXL-JOB user management",
  "summary": "XXL-JOB versions up to and including 3.5.0-SNAPSHOT have insufficient request-forgery defenses for user-management operations. An attacker may cause account-management changes through a victim's browser if the victim interacts with attacker-controlled content while able to access the affected service.",
  "mitigation": "Apply CSRF validation to user-management operations and accept only the intended HTTP methods for state-changing requests. Until a patched release is identified, restrict access to the management interface to trusted users and networks.",
  "vendor": null,
  "product": "XXL-JOB",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R",
  "epss_score": 0.0015,
  "epss_percentile": 0.0362,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.0327792,
  "t0_at": "2026-10-15T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106708"
    }
  }
}

published 2026-10-15 23:34Z
last change 2026-10-21 04:45Z

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.