# CVE-2026-129131: Gameyfin before 2.6.2 Missing Authorization in Hilla Endpoints


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-r2r4-gj52-gh46

## What is CVE-2026-129131?

CVE-2026-129131 is a medium-severity vulnerability in gameyfin, published on 13 Nov 2026. 

### Official description

Gameyfin before 2.6.2 contains a missing authorization vulnerability that allows unauthenticated attackers to bypass login-required mode by calling Hilla endpoints annotated with @AnonymousAllowed. Attackers can POST to synchronous endpoint methods such as GameEndpoint.sync, which LiveSubscriptionSecurity never checks, to retrieve game catalog metadata, libraries, platforms, plugins and game requests.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-129131?

1 open source package ship an affected version, including gameyfin/gameyfin.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `gameyfin/gameyfin` | GitHub | `pkg:github/gameyfin/gameyfin` | All versions | 2.6.2 |

## How do I fix CVE-2026-129131?

Upgrade gameyfin/gameyfin to 2.6.2 or later.

## Is CVE-2026-129131 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129131 exists.

Public exploit code:

- Gameyfin < 2.6.2 - Missing Authorization in Synchronous Hilla Endpoints (nuclei): http/cves/2026/CVE-2026-129131.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129131 and fix it if it is affected.

What it is: CVE-2026-129131 is a medium-severity vulnerability in gameyfin, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129131 exists.

Affected packages and fixed versions:
- gameyfin/gameyfin (GitHub): affected all versions; fixed in 2.6.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129131/ (Markdown: https://insights.sbomify.com/CVE-2026-129131/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129131
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129131
- OSV: https://osv.dev/vulnerability/CVE-2026-129131

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129131/
Summaries are generated and may contain mistakes; the official description above is the record.
