Skip to content
Fencer Vulns
medium 5.3

CVE-2018-17175 json

In marshmallow library the schema "only" option treats an empty list as implying no "only" option

published 2018-09-18 8 y ago modified 2026-06-17 4 mo ago also GHSA-9q2p-fj49-vpxj , PYSEC-2018-67 , EUVD-2018-0090

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

In the marshmallow library before 2.15.1 and 3.x before 3.0.0b9 for Python, the schema "only" option treats an empty list as implying no "only" option, which allows a request that was intended to expose no fields to instead expose all fields (if the schema is being filtered dynamically using the "only" option, and there is a user role that produces an empty value for "only").

Patch / fix

  • pypi marshmallow 2.15.1, 3.0.0b9
  • marshmallow_project marshmallow 2.15.1, 3.0.0b9
  • python-marshmallow Debian 14, Debian 13, Debian 12 3.0.0b14-1

debian advisories DEBIAN-CVE-2018-17175

  • python-marshmallow Ubuntu Pro 18.04 LTS 3.0.0b3-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2018-17175

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • python-marshmallow openSUSE Tumbleweed 4.3.0-1.2
  • python-marshmallow openSUSE Tumbleweed 3.20.2-2.2

opensuse advisories openSUSE-SU-2026:12017-1openSUSE-SU-2024:14147-1

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-2018-17175 updated cvss 5.9

python-marshmallow: Information leak due to invalid usage of the schema "only" option

  • Red Hat All currently supported Red Hat products
    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

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

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi marshmallow
<2.15.1
>=3.0a0, <3.0.0b9
2.15.1
3.0.0b9

Classification

Weakness
  • CWE-358 Improperly Implemented Security Check for Standard

References

Sources

Fencer Vulns 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.