CVE-2026-76838
Webhook SSRF via redirects to internal/metadata addresses, leaking responses.
Is CVE-2026-76838 being exploited?
Not confirmed. CVE-2026-76838 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-76838?
CVE-2026-76838 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-76838?
Yes. A fix has been recorded for CVE-2026-76838. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76838 affect?
CVE-2026-76838 affects Hi.Events < 1.11.1-beta, Integrations using spatie/laravel-webhook-server, Servers hosting Hi.Events webhook dispatch. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76838?
Upgrade to Hi.Events 1.11.1-beta or apply vendor patch; revalidate hosts and block internal redirects.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SSRF in webhook dispatch: attacker can force server to follow redirects to loopback/private/cloud metadata endpoints and exfiltrate response bodies (sensitive data/credentials).
Immediate action required
- affected< 1.11.1-beta
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.