Improper authentication in Snyk Kubernetes Monitor
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.
Summary
This vulnerability in the Snyk Kubernetes Monitor can result in irrelevant data being posted to a Snyk Organization, which could in turn obfuscate other, relevant, security issues. It does not expose the user of the integration to any direct security risk and no user data can be leaked. To exploit the vulnerability the attacker does not need to be authenticated to Snyk but does need to know the target's Integration ID (which may or may not be the same as the Organization ID, although this is an unpredictable UUID in either case).
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA Snyk Kubernetes Monitor (Snyk) Fixed in 2.0.0
Timeline
- 2026-10-02 Threatist record created from CVE-2023-1065
- 2026-10-03 Alias added: GHSA-8mxq-fgcq-vh7j
- 2026-11-04 EPSS moved to the 50th–90th percentile
References
Sources
- CVE-2023-1065 · CVE Program
- CVE-2023-1065 · NVD
- FIRST EPSS
- GHSA-8mxq-fgcq-vh7j · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences