CVE-2016-3954: PYSEC-2026-1062 - web2py exposure of sensitive information

CVE-2016-3954 · Severity: low · CVSS 3 · Published 2026-07-06

web2py exposure of sensitive information

Technologies: web2py (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2016-3954 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-3954 being exploited in the wild.
How severe is CVE-2016-3954?
Low severity, with a CVSS score of 3, published 6 July 2026.
Which products and versions are affected?
web2py (PyPI) ECOSYSTEM:introduced=0,fixed=2.14.2.
Is there a fix for CVE-2016-3954?
Yes. web2py (PyPI): upgrade to 2.14.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-3954?
Check whether you run web2py (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • web2py (PyPI): upgrade to 2.14.2 or later
    pip install "web2py>=2.14.2"

Affected products

  • web2py (PyPI) ECOSYSTEM:introduced=0,fixed=2.14.2

Identifiers

  • CVE-2016-3954
  • GHSA-jr83-vr4j-mp6p
  • PYSEC-2026-1062

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.