NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2020-24715 — scalyr-agent-2

CRITICAL

CVE-2020-24715 is a critical-severity (CVSS 9.8) CWE-295 vulnerability in scalyr-agent-2. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for scalyr-agent-2 — see the affected versions and patch details below.

Scalyr Agent 2 Missing SSL Certificate Validation

Also known asGHSA-738x-v49g-p6hxPYSEC-2020-252
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk
0.00%0.42%0.84%1.26%0.2%0.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍scalyr-agent-2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The Scalyr Agent before 2.1.10 has Missing SSL Certificate Validation because, in some circumstances, native Python code is used that lacks a comparison of the hostname to commonName and subjectAltName.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIscalyr-agent-2all versions2.1.10pip install --upgrade 'scalyr-agent-2==2.1.10'

Affected Products

1 product · 1 configurations
Application
scalyr agentscalyr
< 2.1.10
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Scalyr Agent before 2.1.10 has Missing SSL Certificate Validation be…

scalyr-static.s3.amazonaws.comNVDSep 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scalyr-agent-2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update scalyr-agent-2 to 2.1.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-24715 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The Scalyr Agent before 2.1.10 has Missing SSL Certificate Validation because, in some circumstances, native Python code is used that lacks a comparison of the hostname to commonName and subjectAltName.
O3 Security · Impact-Aware SCA

Is CVE-2020-24715 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-24715: scalyr-agent-2 — Fixed in 2.1.10