Asset ownership takeover via unauthorized import
Published Feb 28, 2024 · Updated Apr 22, 2025
Incorrect authorization in Apache Superset before 3.0.4 and 3.1.0 allows remote authenticated users to take ownership of imported assets. The dashboard and chart import paths accept an existing object's identifier without verifying that the importer may access it, then permit metadata changes that assign ownership. A low-privilege account with import access is required; the takeover does not bypass separate analytical-data access controls.
Summary
What happened
Incorrect authorization in Apache Superset before 3.0.4 and 3.1.0 allows remote authenticated users to take ownership of imported assets. The dashboard and chart import paths accept an existing object's identifier without verifying that the importer may access it, then permit metadata changes that assign ownership. A low-privilege account with import access is required; the takeover does not bypass separate analytical-data access controls.
The record
- CVE
- CVE-2024-26016
- Published
- Feb 28, 2024
- Updated
- Apr 22, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Superset
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 28, 2024CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.0.4
- Affected versionversion=3.1.0 <3.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo