Pulp
14 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Pulp, a product in the devtools ci space. Use it to gauge the current risk picture and drill into individual advisories.
Pulp CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 14 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High7
- Medium7
Latest CVEs
The 14 most recently published vulnerabilities affecting Pulp.
- CVE-2024-7143Pulpcore: rbac permissions incorrectly assigned in tasks that create objects8.3
- CVE-2018-10917pulp 2.16.x and possibly older is vulnerable to an improper path parsing. A malicious user or a malicious iso feed repository can write to locations accessible to the 'apache' user. This may lead t...6.8
- CVE-2018-1090In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with read access on the distributor/importer. An attacker with AP...5.5
- CVE-2015-5263pulp-consumer-client 2.4.0 through 2.6.3 does not check the server's TLS certificate signatures when retrieving the server's public key upon registration.8.1
- CVE-2015-5153Pulp does not remove permissions for named objects upon deletion, which allows authenticated users to gain the privileges of a deleted object via creating an object with the same name.8.8
- CVE-2016-3704Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.7.5
- CVE-2016-3696The pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key.5.5
- CVE-2016-3095server/bin/pulp-gen-ca-certificate in Pulp before 2.8.2 allows local users to read the generated private key.5.5
- CVE-2016-3107The Node certificate in Pulp before 2.8.3 contains the private key, and is stored in a world-readable file in the "/etc/pki/pulp/nodes/" directory, which allows local users to gain access to sensit...5.5
- CVE-2016-3112client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cert.pem as world-readable, which allows remote authenticated users to obtain the consumer...7.5
- CVE-2016-3108The pulp-gen-nodes-certificate script in Pulp before 2.8.3 allows local users to leak the keys or write to arbitrary files via a symlink attack.7.1
- CVE-2016-3111pulp.spec in the installation process for Pulp 2.8.3 generates the RSA key pairs used to validate messages between the pulp server and pulp consumers in a directory that is world-readable before la...5.5
- CVE-2016-3106Pulp before 2.8.3 creates a temporary directory during CA key generation in an insecure manner.5.3
- CVE-2013-7450Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations.7.5
Product grouping is registry-driven, with AI assist and human review. How it works