CVE-2026-123084

Python-pulpcore: pulpcore: header content guard jq filter exposes the content-app environment

  • Medium 6.5

Description

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.

Key facts

Published
10 Nov 2026
Last changed
12 Nov 2026
Assigned by
redhat
EPSS
0.312% likely to be exploited in the next 30 days, higher than 24.446% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.5CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

What to do

  • Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unknown
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unknown
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unknown
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unknown
Red HatRed Hat Satellite 6
  • Default status: unaffected
Red HatRed Hat Satellite 6
  • Default status: unaffected
Red HatRed Hat Update Infrastructure 4 for Cloud Providers
  • Default status: unknown
Red HatRed Hat Update Infrastructure 4 for Cloud Providers
  • Default status: unaffected
Red HatRed Hat Update Infrastructure 5
  • Default status: unaffected
Red HatRed Hat Update Infrastructure 5
  • Default status: unaffected
Red HatRed Hat Update Infrastructure 5
  • Default status: unaffected

Timeline

  1. 5 Nov 2026 Reported to Red Hat.
  2. 10 Nov 2026 Made public.
  3. 10 Nov 2026 Published

Weakness

References