{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76838 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76838 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76838 is a high-severity server-side request forgery vulnerability in HiEventsDev Hi.Events, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76838 and fix it if it is affected.\n\nWhat it is: CVE-2026-76838 is a high-severity server-side request forgery vulnerability in HiEventsDev Hi.Events, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76838 in the wild and no public exploit code.\n\nAffected product: HiEventsDev Hi.Events. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76838/ (Markdown: https://insights.sbomify.com/CVE-2026-76838/index.md)","id":"CVE-2026-76838","markdown":"https://insights.sbomify.com/CVE-2026-76838/index.md","name":"CVE-2026-76838","record":{"aliases":["GHSA-j9wc-mrp3-532h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Hi.Events web application","requires_auth":"low_privilege","summary":"Attackers can exploit unvalidated webhook redirects to access internal services and read sensitive data via the webhook logs endpoint.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Hi.Events before 1.11.1-beta Server-Side Request Forgery via Unvalidated Webhook Redirects","id":"CVE-2026-76838","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Grav before 2.0.16 Information Disclosure via offsetGet","id":"CVE-2026-76839"},"packages":[],"prev":{"headline":"Baserow before 2.3.0 Stored Cross-Site Scripting via Rich Text Mention Display Name","id":"CVE-2026-76837"},"products":["Hi.Events"],"published":"2026-08-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-29","vendors":["HiEventsDev"]},"summary":"Attackers can exploit unvalidated webhook redirects to access internal services and read sensitive data via the webhook logs endpoint.","url":"https://insights.sbomify.com/CVE-2026-76838/"}