Quick answers
- Is CVE-2026-93954 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93954 being exploited in the wild.
- How severe is CVE-2026-93954?
- Medium severity, with a CVSS score of 4.3, published 19 September 2026.
- Which products and versions are affected?
- Grimmory-Tools Grimmory up to 3.3.3 and 3.4.1.
- Is there a fix for CVE-2026-93954?
- A patch was published on 2026-09-18: Patch commit 2b66ca6df8110f6b512e030b54c16b9fbe318f17 (PR #2647) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93954 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-93954?
- Check whether you run Grimmory-Tools Grimmory at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authorization check is missing in the GET /api/v1/settings endpoint of the AppSettingController, allowing the endpoint to be queried without proper permission validation. While a previous change moved the OIDC secret into a dedicated setting, the endpoint itself was not restricted, leaving sensitive settings accessible to any remote caller. The vulnerability has been patched and the fix is available in commit 2b66ca6df8110f6b512e030b54c16b9fbe318f17.
Affected products
- grimmory-tools grimmory up to 3.3.3 and 3.4.1
Timeline
- 2026-09-19: disclosed
- 2026-09-18: patched: Patch commit 2b66ca6df8110f6b512e030b54c16b9fbe318f17 (PR #2647)