Release notes

Corda 4.8 release notes

Corda 4.8, released on April 21st 2021, includes several fixes and improvements.

Long-term support release

Corda 4.8 and Corda Enterprise 4.8 are our long-term support (LTS) platform versions.

R3 provides LTS for this release for 30 months starting April 21st 2021. This is 6 months longer than the support periods for previous releases, giving Corda customers extra time to plan for the next upgrade.

Platform version change

Corda 4.8 uses platform version 10.

For more information about platform versions, see Versioning .

Fixed issues

Corda 4.8 fixes:

  • Transaction verification being performed outside of the attachments class loader.
  • Inconsistencies in source code comments.
  • Privileges escalation caused by flows disabling validation.
  • Attachment presence cache containing the attachment contents.
  • Permissions failing for StartFlowWithClientId.
  • Service loader leaking jar_cache handles.
  • A security issue in a Corda dependency.
  • CordaPersistence.transaction failing to flush correctly.

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.