Loading story…
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.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-54690 was publicly reported as a high-severity SSRF vulnerability affecting datamodel-code-generator. The disclosure states that vulnerable versions process attacker-controlled remote schema references, potentially enabling requests to internal resources and information disclosure.
A server-side request forgery flaw involving remote JSON Schema $ref resolution was fixed in datamodel-code-generator 0.61.0. The fix adds protections around remote URL fetching and addresses unsafe default handling of attacker-controlled HTTP or HTTPS references.
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.
2 references tracked. Mallory keeps watching after this page renders.
cvereports.com
Open sourcecvefeed.io
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 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
Firecrawl disclosed and fixed **CVE-2026-72904**, a critical vulnerability in its extraction functionality that allowed arbitrary file read and server-side request forgery through unsafe JSON Schema `$ref` dereferencing. In versions prior to **2.11.32**, the application used `@apidevtools/json-schema-ref-parser` with default resolver behavior, enabling attacker-supplied schemas to resolve local file paths and remote HTTP(S) references. Attackers could hide `$ref` values inside `default`, `const`, or `enum` fields that AJV would not traverse, then force a dereference error so contents from the extract worker filesystem were exposed in API error messages. The fix replaces the external schema dereferencing library with an internal `dereferenceSchema` implementation that only expands **internal JSON Pointer references** within the same document. The new logic preserves unresolved or external references, blocks filesystem and HTTP(S) resolution to prevent file access and SSRF, detects self-referential cycles, and enforces a maximum resolution limit of **50,000** to prevent runaway processing. Tests added with the patch explicitly verify that file-based and network-based `$ref` values remain untouched, and the hardened resolver was integrated into Firecrawl’s schema-processing path.
Aug 11, 2026
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**.
Aug 24, 2026