# CVE-2026-65319: Feedbin Unauthenticated Entry Content Disclosure via GET /api/v2/entries/:id/text

> Unauthenticated attackers can access private article content by bypassing authorization checks on the entries text API endpoint.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-625r-xrww-9rxq

## What is CVE-2026-65319?

CVE-2026-65319 is a high-severity missing authorization vulnerability in Feedbin, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Feedbin (commit 739884a) contains an unauthenticated information disclosure vulnerability that allows unauthenticated attackers to retrieve private article content by sending requests to the entries text API endpoint, which skips the authorization before-action filter entirely. Attackers can iterate sequential integer entry IDs through the GET /api/v2/entries/:id/text endpoint to enumerate and extract plain-text content of all stored articles, including private newsletter content, personal page-saves, and articles from any user's private subscriptions.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

No fix has been published for CVE-2026-65319 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-65319 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65319 is a high-severity missing authorization vulnerability in Feedbin, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65319 exists.

Affected product: Feedbin. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-65319/ (Markdown: https://insights.sbomify.com/CVE-2026-65319/index.md)
```

## Sources

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

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