Quick answers
- Is CVE-2026-66018 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66018 being exploited in the wild.
- How severe is CVE-2026-66018?
- Medium severity, with a CVSS score of 6.5, published 27 July 2026.
- Which products and versions are affected?
- JFrog Artifactory Self-Managed 7.146.0 to 7.146.33, 7.161.0 to 7.161.14.
- Is there a fix for CVE-2026-66018?
- A patch was published on 2026-07-27: Fixed in Artifactory 7.161.15 and 7.146.34. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66018 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-66018?
- Check whether you run JFrog Artifactory Self-Managed 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 information disclosure vulnerability (CWE-200) exists in JFrog Artifactory Self-Managed versions. The flaw allows a remote authenticated attacker with 'Build Reader' or general read access to an ordinary repository to select and retrieve repository parameters from other, potentially protected, builds. This occurs during the retrieval of environment properties, leading to the exposure of build environment secrets. The vulnerability is caused by insufficient isolation between repository environment properties. Patches are available in versions 7.146.34 and 7.161.15.
Affected products
- JFrog Artifactory Self-Managed 7.146.0 to 7.146.33, 7.161.0 to 7.161.14
Timeline
- 2026-07-27: advisory: JFrog published the security advisory and NVD record.
- 2026-07-27: patched: Fixed in Artifactory 7.161.15 and 7.146.34.