Is CVE-2026-57183 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57183 being exploited in the wild.

How severe is CVE-2026-57183?

Medium severity, with a CVSS score of 6.1, published 15 October 2026.

Is there a fix for CVE-2026-57183?

Yes: fixed in 1.69.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-57183 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-57183?

Check whether you run Erudika Scoold 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.

CVE-2026-57183: Scoold authentication bypass in API configuration endpoints

CVE-2026-57183 · Severity: medium · CVSS 6.1 · Published 2026-10-15

Scoold is a Q&A and knowledge-sharing platform used by teams to collaborate and store company information. Prior to version 1.69.1, the application's API configuration endpoints accept forged authentication tokens if an attacker obtains internal signing secrets, allowing them to read sensitive configuration, server logs, and modify administrative settings—bypassing the normal login process entirely.

Technologies: Erudika Scoold. Vendors: Erudika.

Quick answers

Is CVE-2026-57183 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57183 being exploited in the wild.
How severe is CVE-2026-57183?: Medium severity, with a CVSS score of 6.1, published 15 October 2026.
Which products and versions are affected?: Erudika Scoold before 1.69.1.
Is there a fix for CVE-2026-57183?: Yes: fixed in 1.69.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57183 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-57183?: Check whether you run Erudika Scoold 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.

How to fix

Fixed in: 1.69.1

Technical details

The checkApiAuth() method in ScooldUtils.java accepts JWTs signed with app_secret_key or para_secret_key for the /api/config and /api/stats endpoints without validating a registered API-key jti claim, and maps authenticated requests to a hardcoded administrative API_USER account. This check runs even when the scoold.api_enabled configuration flag is false. An attacker with access to either signing secret can forge a valid token and gain administrative API access without a legitimate registered API key or login session.

Affected products

Erudika Scoold before 1.69.1

Timeline

2026-10-15: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.