Loading story…
A high-severity server-side request forgery flaw tracked as CVE-2026-10582 affects Hugo 0.91.0 through 0.165.0. The issue lies in outbound fetches performed by resources.GetRemote, where security.http.urls validates only the supplied URL text and some canonicalized IPv4 variants, but does not resolve hostnames or verify the destination IP at connection time. That gap allows attacker-controlled hostnames to pass policy checks even if they ultimately resolve to loopback, private-network, or cloud-metadata addresses.
If an attacker can influence a URL through front matter, site content, or a CMS field, Hugo’s build process can retrieve internal resources and embed the response into the generated static site, creating a path for data exfiltration through published artifacts. Hugo’s security code already includes SSRF-focused checks such as blocking localhost-style URL patterns, userinfo in URLs, and alternate IPv4 encodings, but the advisory says those protections do not enforce dial-time destination validation. The vulnerability is classified as CWE-918 and has been scored 7.4 CVSS v3.1 and 8.3 CVSS v4.0.
See affected versions and whether adversaries are exploiting it.
6 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-10582 was published for a Hugo SSRF vulnerability affecting versions 0.91.0 through 0.165.0. The record states that attacker-controlled URLs in content or CMS fields can cause internal resources to be fetched and embedded into generated static output.
VulnCheck published an advisory describing an SSRF issue in Hugo where resources.GetRemote can fetch internal resources because security.http.urls validates only URL text and not the resolved destination address.
A commit by bep removed tailwindcss from Hugo's default security.exec.allow list. The securityConfig.go reference explicitly labels this change with an August 10, 2026 commit note.
The HTTP client code used for remote fetches in Hugo v0.165.0 is described as having no dial-time hook to validate the actual destination IP address, enabling hostname-based bypass of the outbound URL policy.
In Hugo v0.165.0, the security configuration code enforces URL-pattern checks, blocks localhost and dotted-decimal IP literals, and canonicalizes integer, octal, and hexadecimal IPv4 forms, but the referenced vulnerable behavior remains centered on validating URL text rather than the resolved destination address.
The SSRF issue is reported as affecting Hugo versions 0.91.0 through 0.165.0, establishing that the vulnerable range begins with version 0.91.0.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcevulncheck.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A high-severity server-side request forgery flaw tracked as **CVE-2026-54690** affects `datamodel-code-generator` when it processes attacker-controlled JSON Schema `$ref` values pointing to `http` or `https` URLs. In vulnerable releases, the tool silently resolves remote references during schema processing, allowing outbound requests to arbitrary destinations; one report places the affected range at **0.9.1 through 0.60.x**, while another indicates exposure through **0.61.0**. The issue has a **CVSS v3.1 score of 8.2** and is tied to schema resolution and HTTP fetch logic in files including `jsonschema.py` and `http.py`. Researchers said the vulnerable code passes untrusted URLs directly to the HTTP client, follows redirects, and does not adequately restrict hostnames, ports, or IP ranges, creating a path to reach internal services such as `127.0.0.1` and cloud metadata endpoints like `169.254.169.254`. Fetched content may also be incorporated into generated output, raising information disclosure risk in addition to SSRF. The issue is fixed in **version 0.61.0**, with the patch adding URL validation and blocking localhost-style and non-global IP targets unless private-network access is explicitly enabled; recommended mitigations include disabling remote reference resolution or blocking private-network access.
Jul 29, 2026
A high-severity server-side request forgery vulnerability, **CVE-2026-54691**, was disclosed in `datamodel-code-generator`, affecting versions `0.9.1` through `0.60.x`. The flaw stems from the tool's HTTP fetch logic accepting user-supplied `--url` targets and redirect destinations without validating the host or IP address, allowing requests to reach **localhost**, loopback, private, link-local, metadata, and other non-public network resources. The issue is rated **CVSS 8.2** and is considered remotely exploitable. The project addressed the issue in version `0.61.0` with changes that block HTTP(S) requests to non-public network targets by default and validate redirect destinations before following them. The patch also introduced `--allow-private-network` and `--no-allow-private-network` options so users can explicitly opt in to trusted internal schema endpoints, while preserving public remote schema and `$ref` fetching behavior with warnings and updated tests, documentation, and CLI/config handling.
Jul 29, 2026
A high-severity server-side request forgery flaw tracked as **`CVE-2026-67201`** affects the V programming language through version **0.5.2**, allowing remote attackers to bypass host-based allowlists. The issue arises from a parser differential between **`net.urllib`** and **`net.http`**: `net.urllib.parse()` can validate a seemingly trusted host, while `net.http.get()` later normalizes a backslash in the URL authority field and connects to an internal destination instead. The vulnerability was addressed in merged commit **`85859f0`** through a change titled **"net.urllib: reject backslashes in URL authorities"**, with accompanying tests for `vlib/net/urllib` and `vlib/net/http`. Published guidance recommends upgrading to a patched release and reviewing applications to ensure URL normalization and host validation are performed consistently across parsing and request-handling components.
Jul 30, 2026