Quick answers
- Is CVE-2026-42018 exploited in the wild?
- Yes. CVE-2026-42018 is known to be exploited in the wild, first recorded on 11 September 2026. Treat it as urgent.
- How severe is CVE-2026-42018?
- Critical severity, with a CVSS score of 7.5, published 12 August 2026.
- Which products and versions are affected?
- JFrog Artifactory.
- Is there a fix for CVE-2026-42018?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-42018 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-42018?
- Check whether you run JFrog Artifactory. 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
JFrog Artifactory contains an improper authentication vulnerability in its token issuance mechanism. The vulnerability allows an unauthenticated attacker to request an internal anonymous-user token even when anonymous access is explicitly disabled in the configuration. The flaw stems from insufficient validation of authentication state during token generation. Attackers can exploit this over the network without authentication or user interaction to obtain valid tokens that grant access to the repository. Successful exploitation enables unauthorized access to private artifacts, metadata, and build information. This vulnerability has been observed being actively exploited in the wild. Patches are available from JFrog.
Affected products
- JFrog Artifactory
Timeline
- 2026-09-11: disclosed
- exploited: Reported exploited in the wild