Liberica JDK 27.0.1.1+5: Release Notes

Published: November 17, 2026

1. Version information

This document provides information about an unscheduled patch release for vulnerability fixes in Liberica JDK 27.0.1.1. The full version string for this update release is 27.0.1.1+5. The version number is 27.

Liberica JDK 27 is distributed as .apk, .rpm, .zip, .deb, .pkg, and .tar.gz packages. Please select the most appropriate for your purposes.

2. What’s New

This release contains the following updates and new features.

Discontinued OS support

Note that Liberica JDK 27.0.1.1 is not available for and cannot be run on the following operating systems:

  • Windows x86 (32-bit)

  • macOS 10.x

IANA TZ Data version

This release of Liberica JDK 27.0.1.1 comes with the 2026f version of the in-tree copy of the Time Zone Database. The following are the key features of this version.

Briefly

  • Cuba will not fall back 2026-11-01; stays on -04 through 2027-11-07.

  • No more leap seconds, and leap second tables no longer expire.

  • Improve 1965/1966 data for Brazil.

Changes to future timestamps

Cuba will not fall back to -05 on 2026-11-01 and instead plans to maintain -04 through 2027-11-07.

Changes to past timestamps

In 1965 Brazil ended DST on 03-31 at 24:00 not 00:00, and in 1966 it ended DST on 03-01 at 01:00 not 00:00. (Thanks to Daniel Dias Rodrigues.)

Changes to code

zic now ignores Expires lines, as leap second tables in TZif files no longer expire now that there are no more leap seconds; see Internet RFC 9636 §3.2. (Thanks to Garrett Wollman for the heads-up re no more leap seconds.)

localtime.c no longer supports 49 leap seconds, as 27 now suffice. zic now warns if you go over the new limit.

A new compile-time flag -DMIN_TRANSITION_GAP=N specifies a minimum transition gap of N seconds when reading TZif files. It currently defaults to 0, but can be set to 1 if TZif files generated by zic 2021b and earlier are no longer of concern.

With 32-bit time_t, localtime.c functions now check for transition ordering in TZif data as carefully as they do with 64-bit time_t. (Problem reported by Ana Bobillo.)

On platforms like FreeBSD that have O_RESOLVE_BENEATH but lack O_REGULAR, localtime.c compiled with -DOPENAT_TZDIR now checks that a TZ setting with ".." components names a regular file before opening it in an unprivileged program, as it already did for other settings that might name a file outside TZDIR. This fixes a bug introduced in 2026c. (Thanks to Ana Bobillo.)

Changes to documentation and commentary

Documentation and commentary now reflect leap seconds’ demise.

Changes to commentary

Discussion on timekeeping in northwestern Ontario has been updated to reflect that provincial regulation has been issued to allow these areas to stay aligned with America/Winnipeg and follow Manitoba’s adoption of year-round -05 after all. (Thanks to Aoun Khan, Chris Walton, and Heitor David Pinto.)

Discussion on timekeeping in Saskatchewan has been updated to document its new Time Act, 2026 which comes into force on 2026-10-30. (Thanks to Heitor David Pinto.) No change is expected.

NOTE FOR TEMPORARY HACKS FOR CLDR AND CANADA:

This version continues to have temporary hacks to work around Canadian timekeeping bugs in Unicode CLDR releases before CLDR 49 (2026-10-22). These temporary hacks are planned to be removed soon, as they also cause zic versions 2023d through 2026a, in their default mode that generates slim output, to generate TZif files that violate Internet RFC 9636 §3.3. The buggy files in turn cause some TZif readers, including tzcode itself, to ignore some 2026-11-01 02:00 transitions to from their old DST to their new standard times and abbreviations. Although the buggy files do not cause any known TZif reader to mishandle UT offsets, caution is advised when using zic 2023d through 2026a to compile data from more-recent tz releases. To work around this problem when using these older zic versions, use zic -b fat.

For more information, see JDK-8396048.

3. Known Issues

This release does not contain any known issues.

4. Fixed CVEs

This is the list of the security issues fixed in this release. CVSS scores are provided using the CVSS version 3.1 scoring system.

CVE IDCVSS scoreComponentModuleAttack VectorComplexityPrivilegesUser InteractionScopeConfidentialityIntegrityAvailability

CVE-2026-114938

8.1

hotspot

compiler

network

high

none

none

unchanged

high

high

high

CVE-2026-114939

7.4

security-libs

org.ietf.jgss

network

high

none

none

unchanged

high

high

none

CVE-2026-114940

7.4

security-libs

javax.net.ssl

network

high

none

none

unchanged

high

high

none

CVE-2026-114941

7.0

hotspot

compiler

network

high

none

none

unchanged

low

low

high

CVE-2026-114942

7.0

core-libs

network

high

none

none

unchanged

low

low

high

CVE-2026-114943

6.5

hotspot

runtime

network

high

none

none

unchanged

none

low

high

CVE-2026-114944

5.9

core-svc

java.lang.management

network

high

none

none

unchanged

none

high

none

CVE-2026-114945

5.3

core-libs

java.lang

network

low

none

none

unchanged

none

low

none

CVE-2026-114946

4.8

hotspot

compiler

network

high

none

none

unchanged

low

low

none

CVE-2026-114947

3.7

security-libs

javax.net.ssl

network

high

none

none

unchanged

none

low

none

CVE-2026-86144

7.5

javafx

web

network

high

none

required

unchanged

high

high

high

5. Resolved Issues

JDK issues

This is the list of general JDK issues fixed in this release.

Issue IDSummary

JDK-8387162

Enhance Kerberos tickets

JDK-8387351

Enhance TLS connections

JDK-8387541

Enhance StringBuilder checks

JDK-8389830

Enhance JFR Events

JDK-8389989

Enhance loop handling

JDK-8390694

Enhance vector masks

JDK-8391595

[REDO] Enhance JMX Connections

JDK-8392377

(tz) Update Timezone Data to 2026d

JDK-8392519

Cherry-pick metazone changes from CLDR for tzdata2026d, for JDK update release

JDK-8392526

Cherry-pick BCP 47 time zone changes from CLDR for tzdata2026d, for JDK update releases

JDK-8392538

Align the JDK with Microsoft’s new timezone names for British Columbia/Alberta

JDK-8392979

Update the Nov CPU26_11 release date to the newly created stabilization branches

JDK-8393195

Update Libpng to 1.6.59

JDK-8393212

Base64 optimization improvements

JDK-8393337

(tz) Update Timezone Data to 2026e

JDK-8393344

Cherry-pick metazone changes from CLDR to support tzdata2026e for JDK update releases

JDK-8393456

Improve TLS client connections

JDK-8393848

Align the JDK with Microsoft’s new timezone name for Manitoba

JDK-8394492

Update FreeType to 2.15.0

JDK-8395142

CA Enhancements

JDK-8395690

CA certificate improvements

JDK-8396048

(tz) Update to tzdata2026f

JFX issues

This is the list of JFX issues fixed in this release.

Issue IDSummary

JDK-8389783

Crash in JavaFX native glass toolkit during Timer shutdown

JDK-8392009

Update libxml2 to 2.15.4

6. Updates to Third Party Libraries

This is the list of changes in the third party libraries.

LibraryFull nameNew VersionModuleJBS number

FreeType

FreeType

2.15.0

java.desktop

JDK-8394492

Libpng

Libpng

1.6.59

java.awt

JDK-8393195

7. Upgrading to the New Version

To keep your Liberica JDK up-to-date and secure, always upgrade to the newest available version once it is released. To upgrade, install the new version over the previous one. For the installation instructions, see Liberica JDK Installation Guide.

ON THIS PAGE