dbcve.org
Mulesoft Anypoint Code BuilderApplication · Salesforce

CVE-2025-64318

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 1.12.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper Neutralization of Input Used for LLM Prompting vulnerability in Mulesoft Anypoint Code Builder allows manipulation of writeable configuration files through crafted input to the LLM prompting mechanism.

MitigationUpgrade Mulesoft Anypoint Code Builder to version 1.12.1 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mulesoft Anypoint Code BuilderApplication
Affected:< 1.12.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Anypoint Code Builder version
    Check the installed version through your IDE's extension/plugin manager (VS Code Extensions view or Eclipse About dialog). Look for 'Anypoint Code Builder' and note the version number displayed.
    Affected if The displayed version is lower than 1.12.1 (e.g., 1.12.0, 1.11.0, etc.)
  2. Locate extension/plugin files
    Find the Anypoint Code Builder extension installation directory. In VS Code, this is typically in ~/.vscode/extensions or %USERPROFILE%\.vscode\extensions. Look for folders containing 'anypoint' or 'mulesoft' in the name.
    Affected if The extension is installed and the version file inside shows a version below 1.12.1
  3. Verify LLM prompting feature is configured
    Check project or workspace settings for LLM-related configurations. Look for files like .anypoint/config, anypoint-code-builder.json, or similar configuration files that reference AI/LLM settings, prompt templates, or API configurations.
    Affected if LLM prompting or AI assistance features are enabled in the project configuration
  4. Identify writeable config files in workspace
    Review the project directory for configuration files that Anypoint Code Builder can modify. Check for JSON, YAML, or XML config files in src/, config/, or root project directories that have write permissions.
    Affected if The workspace contains writeable configuration files (JSON, YAML, XML) that the LLM feature can access and modify

Your environment is affected if Anypoint Code Builder is installed with a version below 1.12.1 AND the LLM prompting feature is actively used with writeable configuration files present in the workspace.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.12.1 or later
Fixed in 1.12.1
Interim mitigation

Upgrade Mulesoft Anypoint Code Builder to version 1.12.1 or later to remediate this vulnerability.

Recommended fix High confidence

1.12.1

  1. Check the current version of Mulesoft Anypoint Code Builder by accessing the product or its documentation
  2. Navigate to the official Mulesoft or Salesforce documentation for Anypoint Code Builder installation and upgrade instructions
  3. Locate the upgrade path to version 1.12.1 or later
  4. Follow the documented upgrade procedure to update Anypoint Code Builder to version 1.12.1
  5. After upgrading, verify the new version is installed correctly
  6. Test that Anypoint Code Builder functions normally after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mulesoft Anypoint Code Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64318 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data