VaultCode Release Notes

• EULA: https://www.securosys.com/eula
• Documentation: https://docs.securosys.com/vaultcode/overview

2.3.0 (2026-08-31)

New features:

• Added validation to /api/v1/execute endpoint

2.2.2 (2026-08-24)

New features:

• Added ML-DSA support for VaultCode output and evidence signing keys, including the ML_DSA_44, ML_DSA_65, and ML_DSA_87 parameter sets.
• Added ML-DSA support for request signatures.
• Added configurable executable JVM heap, process/thread, and concurrent execution limits under vaultcode.execution.
• Added selectable Swagger examples for /api/v1/execute, with and without requestSignature.

Fixes:

• Added endpoint and request-body validation.

2.2.1 (2026-06-29)

New features:

• Added default HSM host and port values for VaultCode running inside VaultContainers.

2.2.0 (2026-06-09)

New features:

• Added optional stateful HSM executions. VaultCode can pass an execution HSM partition connection to executable JARs when vaultcode.allowExecutableToConnectToPartition is enabled.
• Added new hsm.primary and hsm.execution configuration format for separating the VaultCode HSM partition from the optional execution partition.
• Added attestation signature and attestation certificate chain data to the public key response.

Fixes:

• Added a clear error when executing without a loaded JAR file.

2.1.2 (2026-02-25)

Fixes:

• Fix JAR signature verification failing
• Optimized debug logs - less Spring info, input is not Base64 string

2.1.1 (2026-01-07)

Fixes:

• Create keys (for output, evidence, ...) as normal keys, instead of as SKA keys.

2.1.0 (2025-12-03)

New features:

• Block "executable logs" on HSM image
• Change key type for all type of keys
• Change signature algorithm for all type of keys

Fixes:

• Change hsm port in application-hsm.yml

2.0.2 (2025-11-05)

Fixes:

• Concurrently PostgreSQL create/remove sandbox user

2.0.1 (2025-10-27)

• Updated dependencies

2.0.0 (2025-10-21)

Initial public release.