CVE-2026-76838

HIGHPre-NVD 8.58.5
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. the CNA's CVSS baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this week
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Hi.Events validates a webhook destination only when it is registered, never when it is used. NoInternalUrlRule in backend/app/Validators/Rules/NoInternalUrlRule.php resolves the hostname with gethostbyname() and rejects private and reserved ranges, which any public hostname passes. At dispatch, WebhookDispatchService takes the stored URL and calls it through spatie/laravel-webhook-server without repeating the check, and backend/config/webhook-server.php sets no Guzzle options, so redirect following remains enabled by default. A destination that answers with a redirect to a loopback, private or cloud metadata address therefore causes the server to issue that request, and changing the hostname's DNS record after registration reaches the same result because no resolution is repeated. The response is not discarded: WebhookResponseHandlerService stores the body on the webhook log and WebhookLogResource returns it from the webhook logs endpoint, so the requester reads what the internal service replied rather than inferring it. Both event and organizer webhooks share the rule and the dispatch path. Version 1.11.1-beta revalidates at dispatch, pins the validated address, checks every redirect hop, and decodes IPv6 transition addresses that previously bypassed the filter.

CVSS v3
8.5
EG Score
8.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 29, 2026

Advisory Details (5)

Auto-updated Aug 24, 2026
Patch available. Sources: github_commit, github_pr.
generic

Hi.Events before 1.11.1-beta Server-Side Request Forgery via Unvalidated Webhook Redirects | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hi-events-before-beta-server-side-request-forgery-via-unvalidated-webhook-redirects
generic

Hi.Events/backend/app/Validators/Rules/NoInternalUrlRule.php at v.1.11.0-beta · HiEventsDev/Hi.Events · GitHub

https://github.com/HiEventsDev/Hi.Events/blob/v.1.11.0-beta/backend/app/Validators/Rules/NoInternalUrlRule.php
github_commit Patch Available

commit cfbf468bb5b1 (HiEventsDev/Hi.Events)

Patch available: HiEventsDev/Hi.Events v1.11.1-beta (contains commit cfbf468bb5b1)

https://github.com/HiEventsDev/Hi.Events/commit/cfbf468bb5b1
github_pr Patch Available

Fix reported security advisories

Patch available: HiEventsDev/Hi.Events v1.11.1-beta (PR #1311 merged 2026-08-11)

https://github.com/HiEventsDev/Hi.Events/pull/1311
generic

GitHub - HiEventsDev/Hi.Events: Open-source event management and ticket selling platform — perfect for concerts, conferences, and everything in between 🎟️ If you find this project helpful, please consider giving us a star ⭐️ · GitHub

https://github.com/HiEventsDev/Hi.Events

Vendor Advisories for CVE-2026-76838(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 23:35 UTCGHSA enrichment
  3. 2026-08-29 12:01 UTCEG score recompute
  4. 2026-08-29 12:00 UTCGHSA enrichment
  5. 2026-08-29 05:09 UTCEG score recompute
  6. 2026-08-29 05:09 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 17:30 UTCGHSA enrichment
  9. 2026-08-28 05:16 UTCGHSA enrichment
  10. 2026-08-27 17:37 UTCEG score recompute
  11. 2026-08-27 17:37 UTCGHSA enrichment
  12. 2026-08-27 17:16 UTCEG score recompute
  13. 2026-08-27 17:15 UTCGHSA enrichment
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-27 05:26 UTCGHSA enrichment
  16. 2026-08-26 17:48 UTCEG score recompute
  17. 2026-08-26 17:47 UTCGHSA enrichment
  18. 2026-08-26 14:47 UTCEPSS rescore
  19. 2026-08-26 05:09 UTCGHSA enrichment
  20. 2026-08-25 17:31 UTCEG score recompute
  21. 2026-08-25 17:31 UTCGHSA enrichment
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 05:56 UTCEG score recompute
  24. 2026-08-25 05:56 UTCGHSA enrichment
  25. 2026-08-24 18:21 UTCEG score recompute
Show 2 more
  1. 2026-08-24 17:51 UTCEG score recompute
  2. 2026-08-24 17:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76838?
CVE-2026-76838 is a high vulnerability published on August 24, 2026. Hi.Events validates a webhook destination only when it is registered, never when it is used. NoInternalUrlRule in backend/app/Validators/Rules/NoInternalUrlRule.php resolves the hostname with gethostbyname() and rejects private and reserved ranges, which any public hostname passes. At dispatch,…
When was CVE-2026-76838 disclosed?
CVE-2026-76838 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76838 actively exploited?
CVE-2026-76838 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.2% of all scored CVEs.
What is the CVSS score of CVE-2026-76838?
CVE-2026-76838 has a CVSS v4.0 base score of 8.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-76838?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76838, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76838

Explore →

Is Your Infrastructure Affected by CVE-2026-76838?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.