CVE-2026-65319
Unauthenticated API exposes private Feedbin articles via entries/:id/text
Is CVE-2026-65319 being exploited?
Not confirmed. CVE-2026-65319 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-65319?
CVE-2026-65319 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-65319?
Not known from our data. No patch reference has been recorded for CVE-2026-65319, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-65319 affect?
CVE-2026-65319 affects Feedbin (web app), API endpoint: GET /api/v2/entries/:id/text. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65319?
Implement authorization on the endpoint or apply vendor patch; restrict API access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attackers can enumerate entry IDs and retrieve plain-text of private articles, newsletters, and saved pages.
Immediate action required
- affected<= 739884a
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.