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

CVE-2014-3137 — bottle

CRITICAL

CVE-2014-3137 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in bottle. A fix is available for bottle — see the affected versions and patch details below.

Bottle does not properly limit content-types

Also known asGHSA-873q-wpqr-xfgwPYSEC-2014-77
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.1%probability of exploitation in next 30 days
Lower Risk-0.01%
Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk
0.28%1.45%2.62%3.78%0.9%3.1%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

3 pkgs affected
🐍bottle🐍bottle🐍bottle

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

Bottle 0.10.x before 0.10.12, 0.11.x before 0.11.7, and 0.12.x before 0.12.6 does not properly limit content types, which allows remote attackers to bypass intended access restrictions via an accepted Content-Type followed by a ; (semi-colon) and a Content-Type that would not be accepted, as demonstrated in YouCompleteMe to execute arbitrary code.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIbottle≥ 0.10.0&&< 0.10.120.10.12pip install --upgrade 'bottle==0.10.12'
🐍PyPIbottle≥ 0.11.0&&< 0.11.70.11.7pip install --upgrade 'bottle==0.11.7'
🐍PyPIbottle≥ 0.12.0&&< 0.12.60.12.6pip install --upgrade 'bottle==0.12.6'

Affected Products

1 product · 26 configurations
Application
bottlebottlepy
26 versions
0.10.00.10.10.10.20.10.30.10.40.10.50.10.60.10.70.10.80.10.90.10.100.10.11

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update bottle to 0.10.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3137 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

Bottle 0.10.x before 0.10.12, 0.11.x before 0.11.7, and 0.12.x before 0.12.6 does not properly limit content types, which allows remote attackers to bypass intended access restrictions via an accepted Content-Type followed by a ; (semi-colon) and a Content-Type that would not be accepted, as demonstrated in YouCompleteMe to execute arbitrary code.
O3 Security · Impact-Aware SCA

Is CVE-2014-3137 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2014-3137: bottle RCE — Fixed in 0.10.12