# Cobbler before 3.3.0 allows log poisoning

Advisory record · `GHSA-cpqf-3c3r-c9g2`

- **Identifiers:** `GHSA-cpqf-3c3r-c9g2` · `CVE-2021-40323` · `PYSEC-2021-373`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+, CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 5 Oct 2021
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Oct 2021, 17:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.
- CVSS score 9.8 (7.0 or more) and EPSS 0.87 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `cobbler` (PyPI): affected `<3.3.0`; fixed in `3.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Cobbler versions before 3.3.0 are vulnerable to log poisoning. An attacker who can reach the XMLRPC interface can write crafted content into the log file through a method that logs data, and this can lead to remote code execution. The fix is to upgrade cobbler to 3.3.0 or later.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.87, the 99th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:38 UTC: First seen by agentprime
- 31 Oct 2026, 14:38 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-cpqf-3c3r-c9g2)

## Sources

- [GitHub Advisory Database: GHSA-cpqf-3c3r-c9g2](https://github.com/advisories/GHSA-cpqf-3c3r-c9g2)
- [OSV: GHSA-cpqf-3c3r-c9g2](https://osv.dev/vulnerability/GHSA-cpqf-3c3r-c9g2)
- <https://nvd.nist.gov/vuln/detail/CVE-2021-40323>
- <https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a>
- <https://github.com/advisories/GHSA-cpqf-3c3r-c9g2>
- <https://github.com/cobbler/cobbler>
- <https://github.com/cobbler/cobbler/releases/tag/v3.3.0>
- <https://github.com/pypa/advisory-database/tree/main/vulns/cobbler/PYSEC-2021-373.yaml>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cpqf-3c3r-c9g2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cpqf-3c3r-c9g2/>. Everything for agents: <https://agentprime.io/llms.txt>.
