VulnerabilityPublished 4 Nov 2025Updated 11 Nov 2025

CVE-2025-64318: Salesforce Mulesoft Anypoint Code Builder · Improper Neutralization of Input Used for LLM Prompting

Affects Salesforce Mulesoft Anypoint Code BuilderSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.12.1 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
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: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no loss of confidentiality within 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 4 Nov 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 or the CVSS exploit maturity 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

Upgrade mulesoft/anypoint-code-builder to 1.12.1.

Affected software

Product	Affected	Fixed in
npmmulesoft/anypoint-code-builder`pkg:npm/mulesoft/anypoint-code-builder`Other threats	Affected <1.12.1	Fixed in 1.12.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-64318, organizations should immediately update Mulesoft Anypoint Code Builder to version 1.12.1 or later, where the vulnerability has been addressed. In addition to patching, organizations should implement strict input validation and sanitization controls on any inputs used for LLM prompting or configuration management within development tools. Access to writable configuration files should be tightly controlled using role-based access controls and monitored for unauthorized changes. Employing file integrity monitoring solutions can help detect unexpected modifications to configuration files. Network segmentation and limiting exposure of development environments to untrusted networks can reduce the attack surface. Security teams should also audit existing configurations and deployment pipelines for signs of tampering. Finally, educating developers and DevOps personnel about secure handling of inputs and configuration management best practices will help prevent exploitation of similar vulnerabilities in the future.

Description

Improper Neutralization of Input Used for LLM Prompting vulnerability in Salesforce Mulesoft Anypoint Code Builder allows Manipulating Writeable Configuration Files.This issue affects Mulesoft Anypoint Code Builder: before 1.12.1.

Impact

For European organizations, the primary impact of CVE-2025-64318 lies in the potential unauthorized modification of configuration files within the Mulesoft Anypoint Code Builder environment. This can undermine the integrity of development and deployment processes, potentially leading to the introduction of malicious code, misconfigurations, or altered integration workflows. While confidentiality and availability are not directly impacted, the integrity compromise can cascade into broader security risks if altered configurations lead to insecure deployments or operational disruptions. Organizations heavily reliant on Mulesoft for API management and integration may face increased risk of supply chain attacks or operational inconsistencies. Given the network-exploitable nature and lack of required privileges, the vulnerability could be leveraged by remote attackers to target development environments, which are often less hardened than production systems. This risk is particularly relevant for European enterprises in sectors such as finance, telecommunications, and manufacturing, where Mulesoft is commonly used for critical integration tasks.

CWE-1427Improper Neutralization of Input Used for LLM Prompting (opens in a new tab)
Base weakness
The product uses externally-provided data to build prompts provided to large language models (LLMs), but the way these prompts are constructed causes the LLM to fail to distinguish between user-supplied inputs and developer provided system directives.
Architecture and Design
LLM-enabled applications should be designed to ensure proper sanitization of user-controllable input, ensuring that no intentionally misleading or dangerous characters can be included.
Implementation
LLM prompts should be constructed in a way that effectively differentiates between user-supplied input and developer-constructed system prompting to reduce the chance of model confusion at inference-time.
Architecture and Design
LLM-enabled applications should be designed to ensure proper sanitization of user-controllable input, ensuring that no intentionally misleading or dangerous characters can be included.
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

help.salesforce.com/s/articleView?id=005228032&type=1 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2025, 18:55 UTC

WeaknessesCWE-1427

Technical details

References

Community reviews

Related threats