# CVE-2026-117562: rssant 1.9.0 through 1.9.1 Information Disclosure via publish.story_get Endpoint


- **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:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-pvf4-vqj9-938h

## What is CVE-2026-117562?

CVE-2026-117562 is a medium-severity vulnerability in anyant rssant, published on 27 Oct 2026. 

### Official description

rssant 1.9.0 through 1.9.1 contains an authorization bypass vulnerability that allows unauthenticated attackers to read stories from unpublished feeds through the anonymous publish.story_get endpoint. Because UnionStory.get_by_feed_offset ignores the only_publish flag, attackers can enumerate feed IDs and offsets to retrieve private feed stories.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-117562 being exploited?

There is no known exploitation of CVE-2026-117562 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117562 is a medium-severity vulnerability in anyant rssant, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117562 in the wild and no public exploit code.

Affected product: anyant rssant. 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-117562/ (Markdown: https://insights.sbomify.com/CVE-2026-117562/index.md)
```

## Sources

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

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