# CVE-2026-62668: Grav API Plugin: Webhook SSRF via Unrestricted cURL Protocols

> An attacker with webhook write access can exploit unrestricted cURL protocols to read local files and access internal services via Server-Side Request Forgery.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 19 Aug 2026

## What is CVE-2026-62668?

CVE-2026-62668 is a critical server-side request forgery vulnerability in getgrav grav, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site's content. Prior to 1.0.6, the Grav API plugin WebhookController.php accepts webhook URLs after only FILTER_VALIDATE_URL syntax validation, and WebhookDispatcher.php initializes cURL without CURLOPT_PROTOCOLS or CURLOPT_REDIR_PROTOCOLS restrictions. An account with api.webhooks.write can submit file, dict, gopher, private-network, or link-local targets, retrieve local files and delivery response bodies, and pivot requests to internal services or cloud metadata endpoints. This issue is fixed in version 1.0.6.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-62668?


## How do I fix CVE-2026-62668?

No fix has been published for CVE-2026-62668 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62668 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62668 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62668 and fix it if it is affected.

What it is: CVE-2026-62668 is a critical server-side request forgery vulnerability in getgrav grav, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62668 exists.

Affected product: getgrav grav. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62668/ (Markdown: https://insights.sbomify.com/CVE-2026-62668/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62668
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62668
- OSV: https://osv.dev/vulnerability/CVE-2026-62668

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62668/
Summaries are generated and may contain mistakes; the official description above is the record.