Skip to content

Vendor

Pylons vulnerabilities

14 published CVES affecting Pylons, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
14
Critical
0
High
6
Medium
8
Low
0
Unscored
0
CISA KEV
0
Atom feed of Pylons alerts

Products

Latest Pylons CVEs

Newest publication first

  1. MediumCVSS 5.3 EPSS 0.75%

    Pyramid is an open source Python web framework. A path traversal vulnerability in Pyramid versions 2.0.0 and 2.0.1 impacts users of Python 3.11 that are using a Pyramid static view with a full filesystem path and have a index.html file that is located exactly one directory above...

  2. MediumCVSS 5.3 EPSS 0.75%

    A vulnerability was found in Pylons horus and classified as problematic. Affected by this issue is some unknown functionality of the file horus/flows/local/services.py. The manipulation leads to observable timing discrepancy. The complexity of an attack is rather high. The exploi...

  3. HighCVSS 7.5 EPSS 1.8%

    Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one requ...

  4. HighCVSS 7.5 EPSS 2.0%

    Waitress through version 1.3.1 allows request smuggling by sending the Content-Length header twice. Waitress would header fold a double Content-Length header and due to being unable to cast the now comma separated value to an integer would set the Content-Length to 0 internally....

  5. HighCVSS 7.5 EPSS 2.5%

    Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230 which states: "Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR." Unfortunately if...

  6. HighCVSS 7.5 EPSS 2.4%

    Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separ...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.