CVE-2026-58205

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

GHSA-r6x2-w38j-vvq2 ↗EUVD-2026-111407 ↗

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.
JeromeDevome GRR <= 4.4.2
fixed in 4.5.0
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-2808Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 33msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h59m
0
+4h
+6h
+8h
+10h
+12h

description

GRR versions before 4.5.0 are affected by reflected cross-site scripting in maj.php when installation files remain accessible. An attacker may cause script execution in a victim's browser if the victim visits a crafted URL, potentially enabling session compromise or deceptive redirects.

mitigation

Upgrade GRR to version 4.5.0 or later. Remove or restrict access to installation files that remain on the server.

fixed in 4.5.0

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.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 22:26Z
Δ 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-10-27 22:26Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2808",
  "cve_id": "CVE-2026-58205",
  "display_id": "CVE-2026-58205",
  "ghsa_id": "GHSA-r6x2-w38j-vvq2",
  "euvd_id": "EUVD-2026-111407",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Reflected cross-site scripting in GRR",
  "summary": "GRR versions before 4.5.0 are affected by reflected cross-site scripting in maj.php when installation files remain accessible. An attacker may cause script execution in a victim's browser if the victim visits a crafted URL, potentially enabling session compromise or deceptive redirects.",
  "mitigation": "Upgrade GRR to version 4.5.0 or later. Remove or restrict access to installation files that remain on the server.",
  "vendor": "JeromeDevome",
  "product": "GRR",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 4.4.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.5.0"
      ],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.287285033333333,
  "t0_at": "2026-10-27T22:26:14.705000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T22:26:14.705000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T22:26:14.705000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-58205"
    }
  }
}

published 2026-10-28 00:06Z
last change 2026-10-28 02:59Z

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.