Pyramid static view path traversal up one directory

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2023-40587: 0.75% estimated exploitation activity in the next 30 days; percentile 55.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This 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 the location of the static view's file system path. No further path traversal exists, and the only file that could be disclosed accidentally is index.html. Example: And directory tree: Patches Pyramid now will reject any path that contains a null-byte out of caution. While valid in directory/file names, we would strongly consider it a mistake to use null-bytes in naming files/directories. Secondly, Python 3.11, and 3.12 has fixed the underlying issue in os.path.normpath to no longer truncate on the first 0x00 found, returning the behavior to pre-3.11 Python, un an as of yet unreleased version, see: - https://github.com/python/cpython/issues/106242 - https://github.com/python/cpython/pull/106816 At the time the following Python versions are not fixed: - Python 3.11.0 to 3.11.4 - Python 3.12.0a1 to 3.12.0rc1…

Published by the source

25 Aug 2023, 18:49 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-j8g2-6fc7-q8f8

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-j8g2-6fc7-q8f8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-40587

Advisory: Pyramid static view path traversal up one directory
IDs: CVE-2023-40587, GHSA-j8g2-6fc7-q8f8
Record: https://patchnext.com/advisories/cve-2023-40587 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pyramid 2.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pyramid: affected >= 2.0.0, < 2.0.2; fixed in 2.0.2

## Suggested inspection (read-only)
- `python -m pip show pyramid`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pyramid.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-j8g2-6fc7-q8f8 (OSV record GHSA-j8g2-6fc7-q8f8 lists affected ranges: PyPI pyramid >=2.0.0 <2.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-j8g2-6fc7-q8f8 (GitHub-reviewed advisory GHSA-j8g2-6fc7-q8f8 lists affected ranges: PyPI pyramid >=2.0.0 <2.0.2)

Commands are suggestions: review each one before running it.