DataWeave 2.13.0 Release Notes

This MuleSoft programming language simplifies data transformation tasks and serves as Mule runtime’s expression language for configuring components and connectors. Build powerful integration solutions with intuitive scripting capabilities.

For more detail, see DataWeave Language.

October 6, 2026

DataWeave 2.13.0 is bundled with the Mule 4.13.0 release. For details about the Mule release, see Mule Runtime Engine 4.13.0 Release Notes.

What’s New

The 2.13.0 version of DataWeave introduces these new features and enhancements:

JSON Web Token Signing:

DataWeave introduces the dw::util::jwt::HMAC module for creating signed JSON Web Tokens (JWTs) with the HS256, HS384, and HS512 algorithms. See HMAC (dw::util::jwt::HMAC).
DataWeave introduces the dw::util::jwt::RSA module for creating signed JWTs with the RS256, RS384, and RS512 algorithms using unencrypted PKCS#1 or PKCS#8 PEM private keys. See RSA (dw::util::jwt::RSA).

Compatibility

This table specifies which version of DataWeave is bundled with each Mule runtime engine release:

Mule Version	DataWeave Version
4.13	2.13
4.12	2.12
4.11	2.11
4.10	2.10
4.9	2.9
4.8	2.8
4.7	2.7
4.6	2.6
4.5	2.5
4.4	2.4
4.3	2.3
4.2	2.2
4.1	2.1
3.9	1.2
3.8	1.1
3.7	1.0

Fixed Issues

The release addresses these DataWeave issues and incorporates all patch updates from the 2.12.0 DataWeave release through October 2026:

Issue Resolution ID

Issue Resolution	ID
Memory usage for `text/plain` output is reduced.	W-20063270
Eagerly materialize executable Weave reader results.	W-23837275
Thread safety is improved when processing Java map values.	W-23661641
DataWeave tooling now reports design-time warnings when Java classes referenced in `application/java` schemas can’t be found or are inaccessible through JPMS.	W-22797049
DataWeave now filters Java classes in JPMS-unexported packages during Java module resolution, preventing runtime `IllegalAccessException` failures. This behavior is enabled by default on JDK 17 and later with DataWeave language version 2.13 and later. To keep the previous behavior, set `mule.dw.filter_jpms_inaccessible_modules=false`.	W-22779527
Cryptographic security warnings and errors now include call stacks.	W-22144340

Memory usage for text/plain output is reduced.

W-20063270

Eagerly materialize executable Weave reader results.

W-23837275

Thread safety is improved when processing Java map values.

W-23661641

DataWeave tooling now reports design-time warnings when Java classes referenced in application/java schemas can’t be found or are inaccessible through JPMS.

W-22797049

DataWeave now filters Java classes in JPMS-unexported packages during Java module resolution, preventing runtime IllegalAccessException failures. This behavior is enabled by default on JDK 17 and later with DataWeave language version 2.13 and later. To keep the previous behavior, set mule.dw.filter_jpms_inaccessible_modules=false.

W-22779527

Cryptographic security warnings and errors now include call stacks.

W-22144340

Upgrade

This version of DataWeave is bundled with Mule. DataWeave upgrades take place through Mule. See Mule Upgrades and Patch Updates.