Internal service access via DNS rebinding
Published Aug 25, 2026 · Updated Aug 25, 2026
SSRF in the Grav API plugin before 1.0.16 allows remote authenticated users to reach internal services through webhook delivery. WebhookDispatcher::httpPost validates a DNS answer but discards it, then lets cURL resolve the hostname again for the connection. Exploitation requires api.webhooks.write permission, authoritative DNS control, a low TTL, and winning the lookup race; configured headers and body reach the target, with limited response read-back.
Summary
What happened
SSRF in the Grav API plugin before 1.0.16 allows remote authenticated users to reach internal services through webhook delivery. WebhookDispatcher::httpPost validates a DNS answer but discards it, then lets cURL resolve the hostname again for the connection. Exploitation requires api.webhooks.write permission, authoritative DNS control, a low TTL, and winning the lookup race; configured headers and body reach the target, with limited response read-back.
The record
- CVE
- CVE-2026-56708
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- GetGrav
- Product
- Grav
- Classifications
- CWE-367
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.0.16
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo