Vulnerability Reportcheckmarx/ast-cli:2.3.68

checkmarx/ast-cli:2.3.68
digestsha256:b53719f0c91ad2076feb78e3dc7a295638f8f646bbfa99c18efcdefef4449754

Executive Summary

Last scanned:

Threat Score
60/100CAUTION
Reputation
RELIABLE

This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker controlling a malicious server that the CLI contacts could send a crafted compressed response that crashes the CLI or corrupts its memory during a scan, potentially leading to code execution in the scanning environment. The main concern is CVE-2026-111497, which the analysis does not tie to any special configuration, so it should be assumed to apply in normal operation. The image's exposed-surface findings include several high-severity items, so they cannot be dismissed, even though none are known to be actively exploited. Because the container exposes no ports and runs as a nonroot user, the practical exposure depends on the trust placed in the servers it connects to.

Hardening plan for this image · 5 steps. The first cuts risk from 60 to 2.

Included in Pro

Scanning procedure

  1. Vulnerability scan
    Full CVE sweep across OS packages and app dependencies
  2. Exploitability check
    CVEs ranked by exploit probability (EPSS) and matched against CISA KEV
  3. Reachability analysis
    Symbol-level proof: is the vulnerable code even linked and callable in your binaries?
  4. Runtime verification
    Live-container probes: exposed endpoints, feature flags, real defaults
  5. Supply chain analysis
    Base-image lineage, package provenance and signatures — nothing slipped in unnoticed
  6. Hardening recommendations
    A hardened build plan — patch, remove unused packages, lock down the runtime — with parity tests proving nothing broke

Vulnerabilities

Vulnerability Log

11 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2026-111497HIGH7.45
libbrotlicommon1
1.2.0-r6
fixed in 1.2.0-r7
36.0%
High Exploitation Risk
Directly ExposedContext importance: MEDIUM
CVE-2026-111497HIGH7.45
libbrotlidec1
1.2.0-r6
fixed in 1.2.0-r7
36.0%
High Exploitation Risk
Directly ExposedContext importance: MEDIUM
CVE-2026-111497HIGH7.45
libbrotlienc1
1.2.0-r6
fixed in 1.2.0-r7
36.0%
High Exploitation Risk
Directly ExposedContext importance: MEDIUM
CVE-2026-111943MEDIUM5.44
ca-certificates-bundle
20260909-r2
fixed in 20260909-r3
0.3%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2025-11579MEDIUM4.42
github.com/nwaples/rardecode
v1.1.3
No fix yet
0.4%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
GO-2026-5932MEDIUM4
golang.org/x/crypto
v0.58.0
No fix yet
—
Directly Exposed
CVE-2026-33481LOW3.18
github.com/anchore/syft
v1.21.0
fixed in 1.42.3
0.4%
Theoretical Threat
Directly Exposed
CVE-2026-33997LOW2.92
github.com/docker/docker
v28.0.3+incompatible
fixed in 29.3.1
0.4%
Theoretical Threat
Post-Exploit
CVE-2026-41567LOW2.59
github.com/docker/docker
v28.0.3+incompatible
No fix yet
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-42306LOW2.59
github.com/docker/docker
v28.0.3+incompatible
No fix yet
0.1%
Theoretical Threat
Post-Exploit
CVE-2026-41568LOW2.16
github.com/docker/docker
v28.0.3+incompatible
No fix yet
0.1%
Theoretical Threat
Post-Exploit

Want to check another image? Run a full scan with the Docker Security Scanner.