Skip to content

cves: replace pip's vendored msgpack 1.1.2 with >=1.2.1 to fix GHSA-6v7p-g79w-8964 - #250

Merged
kezhenxu94 merged 1 commit into
SkyAPM:mainfrom
tetrateio:cve/upgrade-pip-vendored-msgpack
Sep 7, 2026
Merged

cves: replace pip's vendored msgpack 1.1.2 with >=1.2.1 to fix GHSA-6v7p-g79w-8964#250
kezhenxu94 merged 1 commit into
SkyAPM:mainfrom
tetrateio:cve/upgrade-pip-vendored-msgpack

Conversation

@tetrate-ci

Copy link
Copy Markdown
Contributor

Summary

pip 26.x ships msgpack 1.1.2 in its internal _vendor directory (used for pip's own cache operations). A regular pip install msgpack>=1.2.1 installs a newer user-facing copy but does not touch pip's vendor directory, so vulnerability scanners (trivy, JFrog Xray) still detect the old 1.1.2 in the base image layer.

This PR adds a Dockerfile step that:

  1. Installs msgpack>=1.2.1 to a temporary location
  2. Copies the Python source files into pip's _vendor/msgpack/
  3. Clears the stale bytecode cache
  4. Updates pip's CycloneDX SBOM (bom.cdx.json) to reflect the patched version

CVEs Fixed

CVE ID Severity Package Fixed Version
GHSA-6v7p-g79w-8964 HIGH msgpack (pip vendor) 1.2.1+

Verification

Build and scan:

docker build -t test-r3 .
trivy image --pkg-types library test-r3 2>/dev/null | grep msgpack
# Only msgpack 1.2.2 should appear, no 1.1.2

cc @kezhenxu94

…v7p-g79w-8964

pip 26.x ships msgpack 1.1.2 in its internal _vendor directory (used for pip's
own cache operations). A regular `pip install msgpack>=1.2.1` installs a newer
user-facing copy but does not touch pip's vendor directory, so trivy still detects
the old 1.1.2 in the base image layer.

This fix installs msgpack>=1.2.1 to a temporary location, copies the Python source
files into pip's _vendor/msgpack/, clears the stale bytecode cache, and updates
pip's CycloneDX SBOM (bom.cdx.json) to reflect the patched version.

Fixes: GHSA-6v7p-g79w-8964 (msgpack < 1.2.1 deserialization vulnerability)
Related to tetrateio/tetrate#34613
@kezhenxu94
kezhenxu94 merged commit 426dbee into SkyAPM:main Sep 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants