<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 15 Oct 2026 20:33:25 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-342424</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-342424</link>
      <description>EUVD-2026-342424</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-342424</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54690</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54690</link>
      <description>&lt;p&gt;datamodel-code-generator generates Pydantic v2 models, dataclasses, TypedDict, and msgspec.Struct from OpenAPI, JSON Schema, GraphQL, Avro, Protobuf, and raw JSON, YAML, or CSV. From 0.9.1 until 0.61.0, datamodel-code-generator silently dereferences attacker-controlled JSON Schema $ref HTTP or HTTPS URLs in src/datamodel_code_generator/parser/jsonschema.py through _get_ref_body, and the --allow-remote-refs gate can warn instead of blocking, allowing server-side request forgery through src/datamodel_code_generator/http.py. This issue is fixed in version 0.61.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;datamodel-code-generator generates Pydantic v2 models, dataclasses, TypedDict, and msgspec.Struct from OpenAPI, JSON Schema, GraphQL, Avro, Protobuf, and raw JSON, YAML, or CSV. From 0.9.1 until 0.61.0, datamodel-code-generator silently dereferences attacker-controlled JSON Schema $ref HTTP or HTTPS URLs in src/datamodel_code_generator/parser/jsonschema.py through _get_ref_body, and the --allow-remote-refs gate can warn instead of blocking, allowing server-side request forgery through src/datamodel_code_generator/http.py. This issue is fixed in version 0.61.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54690</guid>
    </item>
    <item>
      <title>GHSA-954p-556p-r752 — datamodel-code-generator vulnerable to SSRF via JSON-Schema `$ref` to HTTP URL (silent by default)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-954p-556p-r752</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: datamodel-code-generator&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;JSON-Schema `$ref` values pointing at HTTP or HTTPS URLs are silently dereferenced by `datamodel-code-generator` with no IP/host validation, no scheme allow-list, and redirects followed unconditionally. The `--allow-remote-refs` gate added in 0.56.0 defaults to `None`, which only emits a deprecation warning and then fetches the URL anyway; only explicit `--allow-remote-refs=false` blocks the request. The fetched body is parsed as a sub-schema and reflected verbatim into the generated `.py` source. As a result, any JSON-Schema document the developer feeds to `datamodel-codegen` — including documents authored by an attacker — can pivot to arbitrary internal addresses and leak the response into the generated code, with no developer cooperation beyond running the tool.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Sink: `src/datamodel_code_generator/parser/jsonschema.py`, `_get_ref_body` (lines 4776–4793, at tag `0.60.1` / commit `a321547e`):&lt;/p&gt;
&lt;p&gt;```python
def _get_ref_body(self, resolved_ref: str) -&amp;gt; dict[str, YamlValue]:
    if is_url(resolved_ref):
        if not resolved_ref.startswith(&amp;#34;file://&amp;#34;) and self.http_local_ref_path is None:
            if self.allow_remote_refs is False:
                raise Error(f&amp;#34;Fetching remote $ref is disabled: {resolved_ref}...&amp;#34;)
            if self.allow_remote_refs is None:
                warn_deprecated(                            # (A) warn only
                    &amp;#34;behavior.remote-ref-default&amp;#34;,
                    details=f&amp;#34;Reference: {resolved_ref}&amp;#34;,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: datamodel-code-generator&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;JSON-Schema `$ref` values pointing at HTTP or HTTPS URLs are silently dereferenced by `datamodel-code-generator` with no IP/host validation, no scheme allow-list, and redirects followed unconditionally. The `--allow-remote-refs` gate added in 0.56.0 defaults to `None`, which only emits a deprecation warning and then fetches the URL anyway; only explicit `--allow-remote-refs=false` blocks the request. The fetched body is parsed as a sub-schema and reflected verbatim into the generated `.py` source. As a result, any JSON-Schema document the developer feeds to `datamodel-codegen` — including documents authored by an attacker — can pivot to arbitrary internal addresses and leak the response into the generated code, with no developer cooperation beyond running the tool.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Sink: `src/datamodel_code_generator/parser/jsonschema.py`, `_get_ref_body` (lines 4776–4793, at tag `0.60.1` / commit `a321547e`):&lt;/p&gt;
&lt;p&gt;```python
def _get_ref_body(self, resolved_ref: str) -&amp;gt; dict[str, YamlValue]:
    if is_url(resolved_ref):
        if not resolved_ref.startswith(&amp;#34;file://&amp;#34;) and self.http_local_ref_path is None:
            if self.allow_remote_refs is False:
                raise Error(f&amp;#34;Fetching remote $ref is disabled: {resolved_ref}...&amp;#34;)
            if self.allow_remote_refs is None:
                warn_deprecated(                            # (A) warn only
                    &amp;#34;behavior.remote-ref-default&amp;#34;,
                    details=f&amp;#34;Reference: {resolved_ref}&amp;#34;,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-954p-556p-r752</guid>
    </item>
    <item>
      <title>PYSEC-2026-3560 — datamodel-code-generator vulnerable to SSRF via JSON-Schema `$ref` to HTTP URL (silent by default)</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3560</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: datamodel-code-generator&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;JSON-Schema `$ref` values pointing at HTTP or HTTPS URLs are silently dereferenced by `datamodel-code-generator` with no IP/host validation, no scheme allow-list, and redirects followed unconditionally. The `--allow-remote-refs` gate added in 0.56.0 defaults to `None`, which only emits a deprecation warning and then fetches the URL anyway; only explicit `--allow-remote-refs=false` blocks the request. The fetched body is parsed as a sub-schema and reflected verbatim into the generated `.py` source. As a result, any JSON-Schema document the developer feeds to `datamodel-codegen` — including documents authored by an attacker — can pivot to arbitrary internal addresses and leak the response into the generated code, with no developer cooperation beyond running the tool.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Sink: `src/datamodel_code_generator/parser/jsonschema.py`, `_get_ref_body` (lines 4776–4793, at tag `0.60.1` / commit `a321547e`):&lt;/p&gt;
&lt;p&gt;```python
def _get_ref_body(self, resolved_ref: str) -&amp;gt; dict[str, YamlValue]:
    if is_url(resolved_ref):
        if not resolved_ref.startswith(&amp;#34;file://&amp;#34;) and self.http_local_ref_path is None:
            if self.allow_remote_refs is False:
                raise Error(f&amp;#34;Fetching remote $ref is disabled: {resolved_ref}...&amp;#34;)
            if self.allow_remote_refs is None:
                warn_deprecated(                            # (A) warn only
                    &amp;#34;behavior.remote-ref-default&amp;#34;,
                    details=f&amp;#34;Reference: {resolved_ref}&amp;#34;,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: datamodel-code-generator&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;JSON-Schema `$ref` values pointing at HTTP or HTTPS URLs are silently dereferenced by `datamodel-code-generator` with no IP/host validation, no scheme allow-list, and redirects followed unconditionally. The `--allow-remote-refs` gate added in 0.56.0 defaults to `None`, which only emits a deprecation warning and then fetches the URL anyway; only explicit `--allow-remote-refs=false` blocks the request. The fetched body is parsed as a sub-schema and reflected verbatim into the generated `.py` source. As a result, any JSON-Schema document the developer feeds to `datamodel-codegen` — including documents authored by an attacker — can pivot to arbitrary internal addresses and leak the response into the generated code, with no developer cooperation beyond running the tool.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Sink: `src/datamodel_code_generator/parser/jsonschema.py`, `_get_ref_body` (lines 4776–4793, at tag `0.60.1` / commit `a321547e`):&lt;/p&gt;
&lt;p&gt;```python
def _get_ref_body(self, resolved_ref: str) -&amp;gt; dict[str, YamlValue]:
    if is_url(resolved_ref):
        if not resolved_ref.startswith(&amp;#34;file://&amp;#34;) and self.http_local_ref_path is None:
            if self.allow_remote_refs is False:
                raise Error(f&amp;#34;Fetching remote $ref is disabled: {resolved_ref}...&amp;#34;)
            if self.allow_remote_refs is None:
                warn_deprecated(                            # (A) warn only
                    &amp;#34;behavior.remote-ref-default&amp;#34;,
                    details=f&amp;#34;Reference: {resolved_ref}&amp;#34;,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3560</guid>
    </item>
  </channel>
</rss>
