Skip to content
Fencer Intel
medium 6.5

CVE-2026-123084 json

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

published yesterday modified yesterday also EUVD-2026-123048

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

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.

Is CVE-2026-123084 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-123084 updated cvss 6.5

python-pulpcore: pulpcore: Header content guard jq filter exposes the content-app environment

  • Red Hat Ansible Automation Platform 2 python-pulpcore, python3x-pulpcore, python3.11-pulpcore, python3.12-pulpcore, ansible-automation-platform-24/hub-rhel8, ansible-automation-platform-25/hub-rhel8, +2 more
    affected: workaround, no fix available, no fix planned “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.”
  • Red Hat Update Infrastructure 4 for Cloud Providers python-pulpcore
    affected: workaround, no fix planned “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.”
  • Red Hat Satellite 6 python-pulpcore, python3-pulpcore, python3.12-pulpcore Red Hat Update Infrastructure 4 for Cloud Providers python-pulpcore-client Red Hat Update Infrastructure 5 rhui5/rhua-rhel9, rhui5/rhua-tp-rhel9, python-pulpcore-client
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Red Hat Red Hat Ansible Automation Platform 2
  • Red Hat Red Hat Satellite 6
  • Red Hat Red Hat Update Infrastructure 4 for Cloud Providers
  • Red Hat Red Hat Update Infrastructure 5

Classification

Weakness
  • CWE-917 Improper Neutralization of Special Elements used in an Expression Language Statement

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.