# CVE-2026-125750: Firekylin through 2.18.1 Improper Authorization via Admin REST API GET Actions


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-cvf5-89v8-6rq2

## What is CVE-2026-125750?

CVE-2026-125750 is a high-severity vulnerability in Firekylin, published on 10 Nov 2026. 

### Official description

Firekylin through 2.18.1 contains an improper authorization vulnerability that allows editor-role users to read administrator-only secrets because the admin API base guard permits all GET actions. Editors can query options.js for TOTP secrets, push credentials, and cloud storage keys, or user.js for other users' app_key/app_secret to publish posts as administrators via admin/post_push.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-125750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125750 is a high-severity vulnerability in Firekylin, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125750 in the wild and no public exploit code.

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

## Sources

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

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