# CVE-2026-93954: Missing authorization in grimmory

> Remote attackers can access application settings without proper authorization due to missing access controls in the Settings API endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 19 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-h26m-rx2w-qwhg

## What is CVE-2026-93954?

CVE-2026-93954 is a medium-severity missing authorization vulnerability in grimmory-tools grimmory, published on 19 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in grimmory-tools grimmory up to 3.3.3/3.4.1. Affected is the function AppSettingController.getAppSettings of the file backend/src/main/java/org/booklore/controller/AppSettingController.java of the component Settings API Endpoint. Such manipulation leads to incorrect authorization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The name of the patch is 2b66ca6df8110f6b512e030b54c16b9fbe318f17. Applying a patch is advised to resolve this issue. PR #2558, merged as 53abc8b, moved the OIDC secret into a dedicated setting, but did not by itself restrict GET /api/v1/settings.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-93954 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93954 is a medium-severity missing authorization vulnerability in grimmory-tools grimmory, published on 19 Sep 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-93954 exists.

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

## Sources

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

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