How severe is CVE-2018-10931?

CVE-2018-10931 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-10931?

CVE-2018-10931 affects the following packages: cobbler (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2018-10931?

Update cobbler to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-10931 is resolved across your whole dependency graph.

How do I detect CVE-2018-10931 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cobbler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-10931 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2018-10931 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-10931 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-10931?

CVE-2018-10931 has an EPSS (Exploit Prediction Scoring System) score of 68.1%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-10931?

CVE-2018-10931 is classified as CWE-749 (CWE-749). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-10931 published, and has it been updated?

CVE-2018-10931 was published on August 9, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2018-10931 — cobbler

CRITICALFix: cobbler/cobbler#1921

CVE-2018-10931 is a critical-severity (CVSS 9.8) CWE-749 vulnerability in cobbler. EPSS puts its 30-day exploitation probability at 68.1% (99th percentile). A fix is available for cobbler — see the affected versions and patch details below.

Cobbler has Exposed Dangerous Method or Function

Also known asGHSA-8787-63px-3m23PYSEC-2026-313

Published

Aug 9, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

68.1%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍cobbler

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

It was found that cobbler 2.6.x exposed all functions from its CobblerXMLRPCInterface class over XMLRPC. A remote, unauthenticated attacker could use this flaw to gain high privileges within cobbler, upload files to arbitrary location in the context of the daemon.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`cobbler`	≥ 2.6.0&&< 3.0.0	3.0.0`pip install --upgrade 'cobbler==3.0.0'`

Affected Products

2 products · 4 configurations

Application

cobblercobbler_project

≥ 2.6.0 && ≤ 2.6.11

range

Application

satelliteredhat

3 versions

5.65.75.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cobbler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cobbler to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-10931 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

Workaround published by Red Hat

If SELinux is enabled, it might prevent some locations from accepting uploaded files from the attacker. This prevents some basic attacks allowing remote code execution, although it would not exclude all other possibilities.

Source: Red Hat security advisory for CVE-2018-10931 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Satellite 5.6	`cobbler-0:2.0.7-44.1.el6sat`	RHSA-2018:2372

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-10931 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works