LiveActive security incident?Get immediate response
CVE Record

CVE-2018-17175: In the marshmallow library before 2.15.1 and 3.x before 3.0.0b9 for Python, the schema "only" option treats...

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").

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A Python application using affected marshmallow versions could accidentally expose all serialized fields when it intended to expose none. This matters most where field visibility depends on user role or request context, because a low-privilege path could receive more data than designed.

Executive priority

Prioritize remediation for APIs or services that serialize sensitive user, customer, financial, or administrative fields. For internal-only or nonsensitive serializers, handle through normal dependency maintenance after confirming exposure conditions.

Technical view

In marshmallow before 2.15.1 and 3.x before 3.0.0b9, Schema only=[] was treated like no only filter. Dynamic schema filtering that produced an empty only list could serialize all fields instead of zero fields.

Likely exposure

Exposure is limited to applications using affected marshmallow versions and dynamically setting Schema only from roles, permissions, or request-driven field selection. Static schemas or code paths that never produce an empty only list are less likely to be affected.

Exploitation context

The bundle does not show CISA KEV listing, CVSS, CWE, or active exploitation evidence. Abuse would depend on reaching an application path where authorization or filtering logic passes an empty only list to marshmallow serialization.

Researcher notes

This is an application-context information disclosure issue, not a universal marshmallow data leak. The key evidence gap is operational prevalence: sources describe the bug and fixed version boundaries, but not observed exploitation, exploitability metrics, or affected downstream applications.

Mitigation direction

  • Upgrade marshmallow to 2.15.1 or later, or 3.0.0b9 or later for 3.x beta use.
  • Review vendor release notes and project guidance before changing major or beta versions.
  • Avoid treating an empty allowed-field set as a valid all-fields response.
  • Add regression tests for role-based serializers that produce zero allowed fields.

Validation and detection

  • Inventory Python services and dependency locks for marshmallow versions before fixed releases.
  • Search code for Schema construction using dynamic only values.
  • Review role and permission logic that can return an empty field list.
  • Test affected serializers to confirm empty only does not expose all fields.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-17175 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.