CVE-2026-120630

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

GHSA-x35j-64g3-fxg7 ↗EUVD-2026-115354 ↗

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.
CrewAI < 1.15.17
fixed in 1.15.17
ETK-2026-3302Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 14msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h19m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

CrewAI versions before 1.15.17 can be induced to make server-side requests to attacker-chosen URLs because URL checks and HTTP processing can be bypassed. Exploitation requires an attacker to influence a URL processed by the application, such as through functionality using ScrapWebsiteTool.

mitigation

Upgrade CrewAI to version 1.15.17 or later. Until upgraded, restrict untrusted URL input and limit the application’s network access to internal services and metadata endpoints.

fixed in 1.15.17

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3302",
  "cve_id": "CVE-2026-120630",
  "display_id": "CVE-2026-120630",
  "ghsa_id": "GHSA-x35j-64g3-fxg7",
  "euvd_id": "EUVD-2026-115354",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side request forgery in CrewAI URL handling",
  "summary": "CrewAI versions before 1.15.17 can be induced to make server-side requests to attacker-chosen URLs because URL checks and HTTP processing can be bypassed. Exploitation requires an attacker to influence a URL processed by the application, such as through functionality using ScrapWebsiteTool.",
  "mitigation": "Upgrade CrewAI to version 1.15.17 or later. Until upgraded, restrict untrusted URL input and limit the application’s network access to internal services and metadata endpoints.",
  "vendor": "CrewAI",
  "product": "CrewAI",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.15.17"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.15.17"
      ],
      "package_name": "CrewAI",
      "purl": null
    }
  ],
  "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": 24.4211156,
  "t0_at": "2026-11-02T17:37:05.324000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T17:37:05.324000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T17:37:05.324000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-120630"
    }
  }
}

published 2026-11-02 18:32Z
last change 2026-11-02 20:05Z

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.