CVE-2025-52386VulnerabilityPublished 13 Aug 2025

CVE-2025-52386: n/a

Source CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-52386, European organizations should: 1) Avoid processing untrusted or unauthenticated JSON files with CycloneDX Sunshine v0.9 until a patch is available. 2) Implement strict input validation and sanitization to neutralize any formula-like content before exporting to CSV. 3) Educate users to be cautious when opening CSV files from untrusted sources, especially those generated from SBOM tools. 4) Use spreadsheet software settings or plugins that disable automatic formula execution or prompt users before executing formulas in CSV files. 5) Monitor for updates from CycloneDX Sunshine maintainers and apply patches promptly once released. 6) Employ endpoint protection solutions capable of detecting suspicious macro or formula execution behaviors. 7) Consider alternative SBOM tools or newer versions that do not exhibit this vulnerability. 8) Incorporate this vulnerability into supply chain risk assessments and incident response plans to quickly identify and respond to potential exploitation attempts.

Description

CycloneDX Sunshine v0.9 is vulnerable to CSV Formula Injection via a crafted JSON file

Impact

For European organizations, the impact of CVE-2025-52386 can be significant, especially for those involved in software development, supply chain management, or security auditing where CycloneDX Sunshine is used to generate or process SBOMs. Attackers could exploit this vulnerability to execute arbitrary code on systems of analysts or developers who open the malicious CSV files, potentially leading to data breaches, unauthorized access, or lateral movement within corporate networks. Since SBOM tools are increasingly adopted for compliance with European regulations such as the EU Cybersecurity Act and NIS2 Directive, organizations relying on CycloneDX Sunshine may face operational disruptions and compliance risks. The vulnerability could also be leveraged in targeted attacks against software supply chains, which are critical infrastructure components in Europe. The risk is heightened in sectors with stringent data protection requirements under GDPR, where data integrity and confidentiality are paramount. However, the absence of known exploits and the requirement for user interaction somewhat limit immediate widespread impact. Still, the potential for social engineering attacks exploiting this vulnerability remains a concern.

CWE-1236Improper Neutralization of Formula Elements in a CSV File (opens in a new tab)
Base weakness
The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by a spreadsheet product.
Implementation
When generating CSV output, ensure that formula-sensitive metacharacters are effectively escaped or removed from all data before storage in the resultant CSV. Risky characters include '=' (equal), '+' (plus), '-' (minus), and '@' (at).
Implementation
If a field starts with a formula character, prepend it with a ' (single apostrophe), which prevents Excel from executing the formula.
Architecture and Design
Certain implementations of spreadsheet software might disallow formulas from executing if the file is untrusted, or if the file is not authored by the current user.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 13 Aug 2025, 14:34 UTC

WeaknessesCWE-1236

Technical details

References

Community reviews

Related threats