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

CVE-2017-1000007 — txaws

MEDIUMFix: twisted/txaws#26

CVE-2017-1000007 is a medium-severity (CVSS 5.9) Information Exposure vulnerability in txaws. A fix is available for txaws — see the affected versions and patch details below.

txAWS AWSServiceEndpoint defaults to not verifying server certificates

Also known asPYSEC-2017-85
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 29, 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 CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.42%0.84%1.25%0.2%0.8%Apr 26Aug 26Oct 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
🐍txaws

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

txAWS (all current versions) fail to perform complete certificate verification resulting in vulnerability to MitM attacks and information disclosure.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPItxawsall versions0.4.0pip install --upgrade 'txaws==0.4.0'

Affected Products

1 product · 1 configurations
Application
txawstwistedmatrix
all

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update txaws to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000007 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

txAWS fails to perform complete certificate verification resulting in vulnerability to MitM attacks and information disclosure.
O3 Security · Impact-Aware SCA

Is CVE-2017-1000007 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2017-1000007: txaws Info Disclosure — Fixed in 0.4.0