← back to feed
CVE-2026-124617

CVE-2026-124617

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

GHSA-xgqx-465m-4w9g ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
JsonCpp
ETK-2026-4276Zero's internal tracking ID, independent of the CVE number., permanent identifier
14h 26msince last run
4mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
waiting for further signals−1h07mtrigger signal +0h
+3h
+6h
+9h
+12h

description

The supplied record identifies JsonCpp as the associated project but contains no technical vulnerability description. The attacker action, impact, preconditions, and affected releases are not established by the available evidence.

mitigation

Verify the underlying JsonCpp advisory before taking version-specific action. Restrict untrusted JSON processing where feasible until the record’s scope and affected versions are confirmed.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
4m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-12 12:31Z
    ghsa: trigger signal, started the run
    https://github.com/advisories/GHSA-xgqx-465m-4w9g

this entry in the feed

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

{
  "etk_id": "ETK-2026-4276",
  "cve_id": "CVE-2026-124617",
  "display_id": "CVE-2026-124617",
  "ghsa_id": "GHSA-xgqx-465m-4w9g",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Rejected JsonCpp advisory record",
  "summary": "The supplied record identifies JsonCpp as the associated project but contains no technical vulnerability description. The attacker action, impact, preconditions, and affected releases are not established by the available evidence.",
  "mitigation": "Verify the underlying JsonCpp advisory before taking version-specific action. Restrict untrusted JSON processing where feasible until the record’s scope and affected versions are confirmed.",
  "vendor": null,
  "product": "JsonCpp",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 3.6046528166666665,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T12:31:35+00:00",
      "days": -0.5547411954976852,
      "is_lower_bound": true,
      "measured_at": "2026-11-13T01:50:24.685849+00:00",
      "url": "https://github.com/advisories/GHSA-xgqx-465m-4w9g"
    }
  }
}

published 2026-11-12 13:20Z
last change 2026-11-13 01:36Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.