# CVE-2026-61463: Shiori Authenticated Privilege Escalation via PATCH /api/v1/auth/account

> Authenticated users can escalate to administrator by modifying the owner field in the account update endpoint, gaining full system access.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-qhpw-w7p5-4c7m

## What is CVE-2026-61463?

CVE-2026-61463 is a high-severity vulnerability in go-shiori shiori, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Shiori contains a privilege escalation vulnerability in the account update endpoint that allows authenticated users to modify the owner field without authorization checks. Attackers can escalate to administrator by submitting a crafted PATCH request with owner: true, then re-authenticate to obtain an admin JWT token granting full system access.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-61463 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61463 is a high-severity vulnerability in go-shiori shiori, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61463 exists.

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

## Sources

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

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