CVE-2026-123084 · Package
NO FIX YET
The header content guard in Pulpcore saves a jq filter that runs against request headers, and jq's env builtin exposes the server's environment. An attacker who can create a header content guard can read Pulp secrets such as the Django secret key or database password from that environment by repeating requests.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Pulpcore installations where a low-privileged user can create a header content guard and attach it to a distribution. The exposure comes from the jq filter running with access to the content process environment. Installations where only trusted administrators manage content guards carry much less risk.
Not affected if auth-required, default-config
Who cares pulpcore, python, self-hosted
pip show pulpcoreNo fix yet, per the sources.
An expression language injection has been found in the HeaderContentGuard.permit function in publication.py of the content guard in the Pulpcore package. The guard is supposed to check a value in a request header. It saves a jq filter and runs that filter against the header when a client asks for content. The filter is not limited to the header, and jq's env builtin also returns the environment of the content process. A low-privileged network attacker or user who can create a header content guard and attach it to a distribution can save a filter that reads that environment. The content request is allowed or denied according to the filter result. Repeating the request lets that attacker or user recover the environment, including Pulp settings held there, such as the Django secret key or the database password.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.