<?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://db.gcve.eu</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, 31 Oct 2026 12:13:15 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-119285</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-119285</link>
      <description>&lt;p&gt;Fiber is an Express inspired web framework written in Go. From 2.52.1 until 2.52.3, the CORS middleware&amp;#39;s validateDomain wildcard matcher in middleware/cors/utils.go strips the scheme and checks only a host suffix without requiring a dot boundary. An application configured with a wildcard-subdomain AllowOrigins value and AllowCredentials enabled can reflect an unrelated attacker-controlled origin whose host merely ends with the configured base domain. A user who visits that origin can expose authenticated cross-origin responses to the attacker&amp;#39;s page; empty-label origins and later comma-space parsing hardening are outside this advisory. This issue is fixed in version 2.52.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Fiber is an Express inspired web framework written in Go. From 2.52.1 until 2.52.3, the CORS middleware&amp;#39;s validateDomain wildcard matcher in middleware/cors/utils.go strips the scheme and checks only a host suffix without requiring a dot boundary. An application configured with a wildcard-subdomain AllowOrigins value and AllowCredentials enabled can reflect an unrelated attacker-controlled origin whose host merely ends with the configured base domain. A user who visits that origin can expose authenticated cross-origin responses to the attacker&amp;#39;s page; empty-label origins and later comma-space parsing hardening are outside this advisory. This issue is fixed in version 2.52.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-119285</guid>
    </item>
    <item>
      <title>GHSA-g5jq-qmqr-qrwf — Fiber: CORS wildcard origins matched without a dot boundary, allowing credentialed cross-origin reads</title>
      <link>https://db.gcve.eu/vuln/ghsa-g5jq-qmqr-qrwf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gofiber/fiber/v2&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In v2.52.1 and v2.52.2 the CORS middleware matched a wildcard origin such as `https://*.example.com` by suffix only, without a dot boundary and without comparing the scheme. Any origin whose host ends with the base domain, for example `https://evil-example.com` or `http://notexample.com`, was reflected in `Access-Control-Allow-Origin`, together with `Access-Control-Allow-Credentials: true` when `AllowCredentials` is enabled.&lt;/p&gt;
&lt;p&gt;v2.52.3 replaced the matcher (#2915) and is not affected. The report was filed against v2.52.15, where the dot boundary holds; see &amp;#34;Other versions&amp;#34; below.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;v2.52.1 introduced `validateDomain` in `middleware/cors/utils.go` (f0cd3b44, part of the fix for GHSA-fmg4-x8pw-hjhg). It strips scheme and port from both sides and then checks only the suffix, with `trimmedPattern = &amp;#34;example.com&amp;#34;`, so the character before the suffix is never checked:&lt;/p&gt;
&lt;p&gt;```go
if strings.HasPrefix(normalizedPattern, &amp;#34;*.&amp;#34;) {
	trimmedPattern := normalizedPattern[2:]
	if strings.HasSuffix(normalizedDomain, trimmedPattern) {
		if normalizedDomain != trimmedPattern {
			if strings.TrimSuffix(normalizedDomain, trimmedPattern) != &amp;#34;&amp;#34; {
				return true
			}
		}
	}
}
```&lt;/p&gt;
&lt;p&gt;v2.52.3 (1aac6f61, #2915) replaced it with a scheme-aware prefix/suffix split that keeps the leading dot in the suffix (`.example.com`).&lt;/p&gt;
&lt;p&gt;### Proof of concept&lt;/p&gt;
&lt;p&gt;```go
app := fiber.New()
app.Use(cors.New(cors.Config{
	AllowOrigins:     &amp;#34;https://*.example.com&amp;#34;,
	AllowCredentials: true,
}))
app.Get(&amp;#34;/&amp;#34;, fu…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gofiber/fiber/v2&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In v2.52.1 and v2.52.2 the CORS middleware matched a wildcard origin such as `https://*.example.com` by suffix only, without a dot boundary and without comparing the scheme. Any origin whose host ends with the base domain, for example `https://evil-example.com` or `http://notexample.com`, was reflected in `Access-Control-Allow-Origin`, together with `Access-Control-Allow-Credentials: true` when `AllowCredentials` is enabled.&lt;/p&gt;
&lt;p&gt;v2.52.3 replaced the matcher (#2915) and is not affected. The report was filed against v2.52.15, where the dot boundary holds; see &amp;#34;Other versions&amp;#34; below.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;v2.52.1 introduced `validateDomain` in `middleware/cors/utils.go` (f0cd3b44, part of the fix for GHSA-fmg4-x8pw-hjhg). It strips scheme and port from both sides and then checks only the suffix, with `trimmedPattern = &amp;#34;example.com&amp;#34;`, so the character before the suffix is never checked:&lt;/p&gt;
&lt;p&gt;```go
if strings.HasPrefix(normalizedPattern, &amp;#34;*.&amp;#34;) {
	trimmedPattern := normalizedPattern[2:]
	if strings.HasSuffix(normalizedDomain, trimmedPattern) {
		if normalizedDomain != trimmedPattern {
			if strings.TrimSuffix(normalizedDomain, trimmedPattern) != &amp;#34;&amp;#34; {
				return true
			}
		}
	}
}
```&lt;/p&gt;
&lt;p&gt;v2.52.3 (1aac6f61, #2915) replaced it with a scheme-aware prefix/suffix split that keeps the leading dot in the suffix (`.example.com`).&lt;/p&gt;
&lt;p&gt;### Proof of concept&lt;/p&gt;
&lt;p&gt;```go
app := fiber.New()
app.Use(cors.New(cors.Config{
	AllowOrigins:     &amp;#34;https://*.example.com&amp;#34;,
	AllowCredentials: true,
}))
app.Get(&amp;#34;/&amp;#34;, fu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-g5jq-qmqr-qrwf</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-119285</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-119285</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.10: golang-github-gofiber-fiber, Ubuntu:26.10: golang-github-gofiber-fiber-v2&lt;/p&gt;
&lt;p&gt;Fiber is an Express inspired web framework written in Go. From 2.52.1 until 2.52.3, the CORS middleware&amp;#39;s validateDomain wildcard matcher in middleware/cors/utils.go strips the scheme and checks only a host suffix without requiring a dot boundary. An application configured with a wildcard-subdomain AllowOrigins value and AllowCredentials enabled can reflect an unrelated attacker-controlled origin whose host merely ends with the configured base domain. A user who visits that origin can expose authenticated cross-origin responses to the attacker&amp;#39;s page; empty-label origins and later comma-space parsing hardening are outside this advisory. This issue is fixed in version 2.52.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.10: golang-github-gofiber-fiber, Ubuntu:26.10: golang-github-gofiber-fiber-v2&lt;/p&gt;
&lt;p&gt;Fiber is an Express inspired web framework written in Go. From 2.52.1 until 2.52.3, the CORS middleware&amp;#39;s validateDomain wildcard matcher in middleware/cors/utils.go strips the scheme and checks only a host suffix without requiring a dot boundary. An application configured with a wildcard-subdomain AllowOrigins value and AllowCredentials enabled can reflect an unrelated attacker-controlled origin whose host merely ends with the configured base domain. A user who visits that origin can expose authenticated cross-origin responses to the attacker&amp;#39;s page; empty-label origins and later comma-space parsing hardening are outside this advisory. This issue is fixed in version 2.52.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-119285</guid>
    </item>
  </channel>
</rss>
