<?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>Sat, 03 Oct 2026 00:58:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-333703</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-333703</link>
      <description>EUVD-2026-333703</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-333703</guid>
    </item>
    <item>
      <title>fkie_cve-2026-58404</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-58404</link>
      <description>&lt;p&gt;Hugo is a static site generator. From v0.162.0 through v0.163.0, the default security.http.urls policy denies requests to loopback, internal, and cloud-metadata IPv4 literals, but the deny rule only matched dotted-decimal notation, so alternate IPv4 encodings of the same addresses, including integer, hex, or octal, passed the policy. When a template passes an untrusted or data-derived URL to resources.GetRemote and the host platform uses the cgo system resolver, these encodings resolve to the blocked address, allowing build-time server-side requests to loopback and internal services, including the cloud-metadata endpoint in hosted or CI builds; the same check is reused on redirects, so the gap also applies to each redirect hop. This issue is fixed in v0.163.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Hugo is a static site generator. From v0.162.0 through v0.163.0, the default security.http.urls policy denies requests to loopback, internal, and cloud-metadata IPv4 literals, but the deny rule only matched dotted-decimal notation, so alternate IPv4 encodings of the same addresses, including integer, hex, or octal, passed the policy. When a template passes an untrusted or data-derived URL to resources.GetRemote and the host platform uses the cgo system resolver, these encodings resolve to the blocked address, allowing build-time server-side requests to loopback and internal services, including the cloud-metadata endpoint in hosted or CI builds; the same check is reused on redirects, so the gap also applies to each redirect hop. This issue is fixed in v0.163.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-58404</guid>
    </item>
    <item>
      <title>GHSA-r46f-3rpw-hxrv — Hugo: security.http.urls deny rules bypassed by alternate IPv4 encodings (SSRF)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r46f-3rpw-hxrv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gohugoio/hugo&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The default `security.http.urls` policy denies requests to loopback, internal,
  and cloud-metadata IPv4 literals (e.g. `http://127.0.0.1/`,
  `http://169.254.169.254/`). The deny rule only matched dotted-decimal notation,
  so alternate IPv4 encodings of the same addresses — integer, hex, or octal,
  which contain no dot — passed the policy:&lt;/p&gt;
&lt;p&gt;- `http://2130706433/` → `127.0.0.1`
  - `http://2852039166/` → `169.254.169.254` (cloud metadata)
  - `http://0x7f000001/`, `http://017700000001/`, `http://0/`&lt;/p&gt;
&lt;p&gt;When a template passes an untrusted or data-derived URL to
  `resources.GetRemote` and the host platform uses the
  cgo system resolver, these encodings resolve to the blocked address — allowing
  build-time server-side requests to loopback and internal services, including the
  cloud-metadata endpoint in hosted/CI builds. The same check is reused on
  redirects, so the gap also applies to each redirect hop.&lt;/p&gt;
&lt;p&gt;This affects sites that rely on `security.http.urls` as a security boundary
  while fetching attacker-influenced remote URLs; it does not affect sites that
  fully trust the URLs they fetch.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in **v0.163.1**. Integer/hex/octal IPv4 hosts are now canonicalized to
  dotted-decimal before the policy is applied, so every encoding of an address is
  treated alike. No configuration change is required.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Avoid passing untrusted URLs to `resources.GetRemote`, or
  tighten `security.http.urls` to an explicit allow-list…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gohugoio/hugo&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The default `security.http.urls` policy denies requests to loopback, internal,
  and cloud-metadata IPv4 literals (e.g. `http://127.0.0.1/`,
  `http://169.254.169.254/`). The deny rule only matched dotted-decimal notation,
  so alternate IPv4 encodings of the same addresses — integer, hex, or octal,
  which contain no dot — passed the policy:&lt;/p&gt;
&lt;p&gt;- `http://2130706433/` → `127.0.0.1`
  - `http://2852039166/` → `169.254.169.254` (cloud metadata)
  - `http://0x7f000001/`, `http://017700000001/`, `http://0/`&lt;/p&gt;
&lt;p&gt;When a template passes an untrusted or data-derived URL to
  `resources.GetRemote` and the host platform uses the
  cgo system resolver, these encodings resolve to the blocked address — allowing
  build-time server-side requests to loopback and internal services, including the
  cloud-metadata endpoint in hosted/CI builds. The same check is reused on
  redirects, so the gap also applies to each redirect hop.&lt;/p&gt;
&lt;p&gt;This affects sites that rely on `security.http.urls` as a security boundary
  while fetching attacker-influenced remote URLs; it does not affect sites that
  fully trust the URLs they fetch.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in **v0.163.1**. Integer/hex/octal IPv4 hosts are now canonicalized to
  dotted-decimal before the policy is applied, so every encoding of an address is
  treated alike. No configuration change is required.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Avoid passing untrusted URLs to `resources.GetRemote`, or
  tighten `security.http.urls` to an explicit allow-list…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r46f-3rpw-hxrv</guid>
    </item>
    <item>
      <title>RHSA-2026:36862 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:36862</link>
      <description>&lt;p&gt;github.com/gohugoio/hugo: Hugo: Cross-site Scripting via untrusted HTML content files github.com/gohugoio/hugo: Hugo: Cross-site Scripting via unescaped code-fence language in default code block renderer github.com/gohugoio/hugo: Hugo: Information disclosure via symlink confinement bypass in virtual filesystem github.com/gohugoio/hugo: Hugo: Server-Side Request Forgery (SSRF) via alternate IPv4 encodings&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;github.com/gohugoio/hugo: Hugo: Cross-site Scripting via untrusted HTML content files github.com/gohugoio/hugo: Hugo: Cross-site Scripting via unescaped code-fence language in default code block renderer github.com/gohugoio/hugo: Hugo: Information disclosure via symlink confinement bypass in virtual filesystem github.com/gohugoio/hugo: Hugo: Server-Side Request Forgery (SSRF) via alternate IPv4 encodings&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:36862</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-58404</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-58404</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: hugo, Ubuntu:18.04:LTS: hugo, Ubuntu:20.04:LTS: hugo, Ubuntu:22.04:LTS: hugo, Ubuntu:Pro:24.04:LTS: hugo, Ubuntu:25.10: hugo, Ubuntu:26.04:LTS: hugo&lt;/p&gt;
&lt;p&gt;Hugo is a static site generator. From v0.162.0 through v0.163.0, the default security.http.urls policy denies requests to loopback, internal, and cloud-metadata IPv4 literals, but the deny rule only matched dotted-decimal notation, so alternate IPv4 encodings of the same addresses, including integer, hex, or octal, passed the policy. When a template passes an untrusted or data-derived URL to resources.GetRemote and the host platform uses the cgo system resolver, these encodings resolve to the blocked address, allowing build-time server-side requests to loopback and internal services, including the cloud-metadata endpoint in hosted or CI builds; the same check is reused on redirects, so the gap also applies to each redirect hop. This issue is fixed in v0.163.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: hugo, Ubuntu:18.04:LTS: hugo, Ubuntu:20.04:LTS: hugo, Ubuntu:22.04:LTS: hugo, Ubuntu:Pro:24.04:LTS: hugo, Ubuntu:25.10: hugo, Ubuntu:26.04:LTS: hugo&lt;/p&gt;
&lt;p&gt;Hugo is a static site generator. From v0.162.0 through v0.163.0, the default security.http.urls policy denies requests to loopback, internal, and cloud-metadata IPv4 literals, but the deny rule only matched dotted-decimal notation, so alternate IPv4 encodings of the same addresses, including integer, hex, or octal, passed the policy. When a template passes an untrusted or data-derived URL to resources.GetRemote and the host platform uses the cgo system resolver, these encodings resolve to the blocked address, allowing build-time server-side requests to loopback and internal services, including the cloud-metadata endpoint in hosted or CI builds; the same check is reused on redirects, so the gap also applies to each redirect hop. This issue is fixed in v0.163.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-58404</guid>
    </item>
  </channel>
</rss>
