<?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, 08 Oct 2026 04:00:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-343939</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-343939</link>
      <description>EUVD-2026-343939</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-343939</guid>
    </item>
    <item>
      <title>fkie_cve-2026-48031</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48031</link>
      <description>&lt;p&gt;go-base is a Go RESTful API Boilerplate template with JWT Authentication, backed by PostgreSQL. In versions prior to 2026-05-18, the JWT signing secret is hardcoded to the known string &amp;#34;random&amp;#34;, letting any attacker who reads the public repository forge tokens for arbitrary users, including admin roles, and completely bypass authentication on all protected endpoints. This value is set in two places: the dev.env template (line 10) and a programmatic fallback in cmd/serve.go (line 35), so the application uses it even when no .env file is present. The original mitigation in auth/jwt/tokenauth.go (lines 22 to 25) only caught the exact string &amp;#34;random&amp;#34;, letting other weak secrets through, and replaced it with an in-memory key that was not persisted, invalidating all tokens on every restart and effectively causing a denial-of-service. This issue has been fixed in version 2026-05-18.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;go-base is a Go RESTful API Boilerplate template with JWT Authentication, backed by PostgreSQL. In versions prior to 2026-05-18, the JWT signing secret is hardcoded to the known string &amp;#34;random&amp;#34;, letting any attacker who reads the public repository forge tokens for arbitrary users, including admin roles, and completely bypass authentication on all protected endpoints. This value is set in two places: the dev.env template (line 10) and a programmatic fallback in cmd/serve.go (line 35), so the application uses it even when no .env file is present. The original mitigation in auth/jwt/tokenauth.go (lines 22 to 25) only caught the exact string &amp;#34;random&amp;#34;, letting other weak secrets through, and replaced it with an in-memory key that was not persisted, invalidating all tokens on every restart and effectively causing a denial-of-service. This issue has been fixed in version 2026-05-18.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-48031</guid>
    </item>
    <item>
      <title>GHSA-mqq6-462x-jxmm — Go Restful API Boilerplate: Hardcoded JWT Secret "random" Allows Token Forgery</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mqq6-462x-jxmm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/dhax/go-base&lt;/p&gt;
&lt;p&gt;## Vulnerability: CWE-798 — Hardcoded JWT Secret + Broken Mitigation&lt;/p&gt;
&lt;p&gt;### Affected Component
- `github.com/dhax/go-base` — Go REST API boilerplate (go-chi/jwtauth/v5, Viper, PostgreSQL/Bun)
- 1,685 stars on GitHub&lt;/p&gt;
&lt;p&gt;### Vulnerability Locations&lt;/p&gt;
&lt;p&gt;| File | Line | Role |
|------|------|------|
| `dev.env` | 10 | `AUTH_JWT_SECRET=random` — template default shipped to all users |
| `cmd/serve.go` | 35 | `viper.SetDefault(&amp;#34;auth_jwt_secret&amp;#34;, &amp;#34;random&amp;#34;)` — code-level fallback |
| `auth/jwt/tokenauth.go` | 22-25 | Weak mitigation: only checked literal `&amp;#34;random&amp;#34;`, auto-generated non-persistent key |
| `auth/jwt/tokenauth.go` | 28 | `jwtauth.New(&amp;#34;HS256&amp;#34;, []byte(secret), nil)` — creates JWT signer with the weak key |
| `pwdless/api.go` | 203 | `GenTokenPair()` — issues access + refresh tokens signed with the weak key |&lt;/p&gt;
&lt;p&gt;### Data Flow&lt;/p&gt;
&lt;p&gt;```
dev.env AUTH_JWT_SECRET=random
  OR
cmd/serve.go viper.SetDefault(&amp;#34;auth_jwt_secret&amp;#34;, &amp;#34;random&amp;#34;)
    │
    ▼
auth/jwt/tokenauth.go: viper.GetString(&amp;#34;auth_jwt_secret&amp;#34;)
    │
    ▼
auth/jwt/tokenauth.go: jwtauth.New(&amp;#34;HS256&amp;#34;, []byte(secret), nil)
    │
    ▼
pwdless/api.go: GenTokenPair() → access + refresh tokens
    │
    ▼
jwt/authenticator.go: Every authenticated request trusts the forged token
```&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;The JWT signing secret is hardcoded to the string `&amp;#34;random&amp;#34;` in **two independent locations**:&lt;/p&gt;
&lt;p&gt;1. **`dev.env:10`** — The template `.env` file sets `AUTH_JWT_SECRET=random`. Every developer who copies this template gets the same default.&lt;/p&gt;
&lt;p&gt;2. **…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/dhax/go-base&lt;/p&gt;
&lt;p&gt;## Vulnerability: CWE-798 — Hardcoded JWT Secret + Broken Mitigation&lt;/p&gt;
&lt;p&gt;### Affected Component
- `github.com/dhax/go-base` — Go REST API boilerplate (go-chi/jwtauth/v5, Viper, PostgreSQL/Bun)
- 1,685 stars on GitHub&lt;/p&gt;
&lt;p&gt;### Vulnerability Locations&lt;/p&gt;
&lt;p&gt;| File | Line | Role |
|------|------|------|
| `dev.env` | 10 | `AUTH_JWT_SECRET=random` — template default shipped to all users |
| `cmd/serve.go` | 35 | `viper.SetDefault(&amp;#34;auth_jwt_secret&amp;#34;, &amp;#34;random&amp;#34;)` — code-level fallback |
| `auth/jwt/tokenauth.go` | 22-25 | Weak mitigation: only checked literal `&amp;#34;random&amp;#34;`, auto-generated non-persistent key |
| `auth/jwt/tokenauth.go` | 28 | `jwtauth.New(&amp;#34;HS256&amp;#34;, []byte(secret), nil)` — creates JWT signer with the weak key |
| `pwdless/api.go` | 203 | `GenTokenPair()` — issues access + refresh tokens signed with the weak key |&lt;/p&gt;
&lt;p&gt;### Data Flow&lt;/p&gt;
&lt;p&gt;```
dev.env AUTH_JWT_SECRET=random
  OR
cmd/serve.go viper.SetDefault(&amp;#34;auth_jwt_secret&amp;#34;, &amp;#34;random&amp;#34;)
    │
    ▼
auth/jwt/tokenauth.go: viper.GetString(&amp;#34;auth_jwt_secret&amp;#34;)
    │
    ▼
auth/jwt/tokenauth.go: jwtauth.New(&amp;#34;HS256&amp;#34;, []byte(secret), nil)
    │
    ▼
pwdless/api.go: GenTokenPair() → access + refresh tokens
    │
    ▼
jwt/authenticator.go: Every authenticated request trusts the forged token
```&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;The JWT signing secret is hardcoded to the string `&amp;#34;random&amp;#34;` in **two independent locations**:&lt;/p&gt;
&lt;p&gt;1. **`dev.env:10`** — The template `.env` file sets `AUTH_JWT_SECRET=random`. Every developer who copies this template gets the same default.&lt;/p&gt;
&lt;p&gt;2. **…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mqq6-462x-jxmm</guid>
    </item>
  </channel>
</rss>
