CVE-2026-123776

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

GHSA-vx75-vp6j-73h2 ↗EUVD-2026-119210 ↗

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.
RRD-CGI-Image <= 0.01
CWE-1287 Improper Validation of Specified Type of Input
ETK-2026-3831Zero's internal tracking ID, independent of the CVE number., permanent identifier
12h 12msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h51m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

RRD-CGI-Image through version 0.01 can block a CGI worker while processing an untrusted tz-related query parameter. An attacker who can send requests to the affected CGI endpoint may cause request handling to stall.

mitigation

Filter or reject query parameters with names containing "tz" before they reach RRD-CGI-Image, and restrict access to the CGI endpoint to trusted users where possible. No fixed version is recorded; deploy the filter until an updated release is available.

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
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-07 11:51Z
Δ 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-11-07 11:51Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3831",
  "cve_id": "CVE-2026-123776",
  "display_id": "CVE-2026-123776",
  "ghsa_id": "GHSA-vx75-vp6j-73h2",
  "euvd_id": "EUVD-2026-119210",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CGI parameter denial of service in RRD-CGI-Image",
  "summary": "RRD-CGI-Image through version 0.01 can block a CGI worker while processing an untrusted tz-related query parameter. An attacker who can send requests to the affected CGI endpoint may cause request handling to stall.",
  "mitigation": "Filter or reject query parameters with names containing \"tz\" before they reach RRD-CGI-Image, and restrict access to the CGI endpoint to trusted users where possible. No fixed version is recorded; deploy the filter until an updated release is available.",
  "vendor": null,
  "product": "RRD-CGI-Image",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.01"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "RRD-CGI-Image",
      "purl": null
    }
  ],
  "cwes": [
    1287
  ],
  "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": 29.446808933333333,
  "t0_at": "2026-11-07T11:51:18.541000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-07T11:51:18.541000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T11:51:18.541000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123776"
    }
  }
}

published 2026-11-07 12:12Z
last change 2026-11-08 00:08Z

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.