# CVE-2026-130857: EveryDocs Core before 1.6.1 Authorization Bypass via Unscoped Record Lookups


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-fphh-x7fg-5xpm, GHSA-g83j-767p-v5w7

## What is CVE-2026-130857?

CVE-2026-130857 is a high-severity vulnerability in jonashellmann everydocs-core, published on 17 Nov 2026. 

### Official description

EveryDocs Core before 1.6.1 contains an authorization bypass vulnerability that allows authenticated users to access other users' records through unscoped Model.find(params[:id]) lookups in multiple controllers. Self-registered attackers can enumerate sequential ids to read, modify, or delete other users' documents and stored files, and rename or delete their folders, tags and people.

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

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

1 open source package ship an affected version, including jonashellmann/everydocs-core.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `jonashellmann/everydocs-core` | GitHub | `pkg:github/jonashellmann/everydocs-core` | All versions | 1.6.1 |

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

Upgrade jonashellmann/everydocs-core to 1.6.1 or later.

## Is CVE-2026-130857 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130857 is a high-severity vulnerability in jonashellmann everydocs-core, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130857 exists.

Affected packages and fixed versions:
- jonashellmann/everydocs-core (GitHub): affected all versions; fixed in 1.6.1

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

## Sources

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

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