[dependabot]

Bumps the minor-and-patch group with 15 updates in the / directory:

Package	From	To
org.projectlombok:lombok	1.18.46	1.18.48
org.springframework.boot:spring-boot-dependencies	4.1.1	4.1.2
tools.jackson:jackson-bom	3.1.7	3.2.4
org.apache.tomcat.embed:tomcat-embed-core	11.0.25	11.0.27
org.apache.tomcat.embed:tomcat-embed-websocket	11.0.25	11.0.27
org.postgresql:postgresql	42.7.13	42.7.14
gradle-wrapper	9.7.0	9.8.2
com.hierynomus:sshj	0.40.0	0.41.2
com.github.mwiede:jsch	2.28.6	2.28.8
org.eclipse.jgit:org.eclipse.jgit	7.7.1.202607240634-r	7.8.0.202609011348-r
org.bouncycastle:bcpkix-jdk18on	1.85	1.86
com.fasterxml.jackson.core:jackson-databind	2.22.3	2.22.4
com.fasterxml.jackson.datatype:jackson-datatype-jsr310	2.22.3	2.22.4
com.fasterxml.jackson.datatype:jackson-datatype-jsr310	2.22.3	2.22.4
org.slf4j:slf4j-api	2.0.18	2.0.20
org.slf4j:slf4j-simple	2.0.18	2.0.20
org.slf4j:slf4j-simple	2.0.18	2.0.20

Updates org.projectlombok:lombok from 1.18.46 to 1.18.48

Changelog

Sourced from org.projectlombok:lombok's changelog.

v1.18.48 (September 1st, 2026)

• BREAKING CHANGE/BUGFIX: @Builder(builderClassName = "Builder") now generates an error, because the type names collide. #3857 (found after release)
• PLATFORM: JDK27 support added #4072.
• BUGFIX: @SneakyThrows usage on JDK26 no longer results in class files that require lombok.jar to be on the runtime classpath (which should not be neccessary). #4040.
• FEATURE: New config key lombok.checkReturnValueAnnotation (values: none, lombok; default: none) lets lombok generate @lombok.CheckReturnValue on generated methods where the return value should not be ignored, such as @With methods and @Builder.build(). A future lombok release may flip the default to lombok. #4013.
• PROMOTION: @SuperBuilder has been promoted to the main package. Otherwise, no changes have been made to the annotation. The old experimental annotation will remain for a few versions, at which point it will be marked as a deprecated annotation. Eventually it'll be removed. If you had lombok.config configuration for this annotation, the configuration keys for this feature have been renamed. #2209.
• OLD-CRUFT: lombok.experimental.Wither and lombok.Delegate are deprecated remnants; these features were moved (to respectively lombok.With and lombok.experimental.Delegate over 5 years ago. They are now removed entirely. If your project is dependent on an older version of lombok which still has those; fret not, lombok still processes these annotations. It just no longer includes them in the jar.
• FEATURE: CheckerFramework: Lombok now adds @SideEffectFree to constructors it makes if you have enabled checker framework via lombok.config.
• BUGFIX: CheckerFramework: Lombok would add @SideEffectFree to the build() method of any generated builder, even if it is a builder for invoking a method; in that case, the side-effect-free nature of build() mirrors the side-effect-free nature of the method invocation you've built. Lombok now checks if the method it generated a builder for is side effect free / 'check return type'.

Commits

• b48657c [version] pre-release version bump v1.18.48
• d1d0039 Merge branch 'jdk27'
• 1a23dad [review][refactor] No meaningful changes: Improved comments, javadoc, and cle...
• 40cdde8 [changelog] JDK27 support
• 25eae29 Add Danish Nawab to AUTHORS
• 10ab92b Support JDK27: end positions moved from EndPosTable to JCTree.endpos
• af01b7a Document the new configuration syntax for listy things
• 1be3857 There is no more HtAccess
• 405985d Semantic sections for website
• 04b7340 [trivial] fixing some outdated tests (tests were broken, not lombok).
• Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-dependencies from 4.1.1 to 4.1.2

Release notes

Sourced from org.springframework.boot:spring-boot-dependencies's releases.

v4.1.2

⭐ New Features

• Add TWENTY_SEVEN to JavaVersion enum #51426

🐞 Bug Fixes

• OriginTrackedResource does not implement equals correctly #52267
• OriginTrackedPropertiesLoader drops properties whose name starts with # or ! #52265
• JWTs are rejected when issuer-uri is empty and jwk-set-uri is set #52260
• Package manifest attributes are missing for nested jars without directory entries #52258
• Logback ColorConverter unnecessarily parses its options for every log event #52228
• Empty system property in TestPropertyValues is cleared instead of being restored to its empty value #52208
• Graceful shutdown of Tomcat or Jetty may call back with REQUESTS_ACTIVE when stop is called immediately after shutDownGracefully on an idle server #52197
• NettyWebServer stop may hang when called immediately after shutDownGracefully #52196
• gRPC client 'grpc' load balancing fails to bind with a NullPointerException when no child policies are configured #52193
• Prevent gRPC client properties from overriding user customizations #52175
• MongoDB fails to connect when credentials contain a space #52168
• Authentication fails when password configured in spring.elasticsearch.uris contains a colon #52166
• Logging can be lost when a context is paused by the test context framework #52088
• Docker Compose support for MongoDB fails to connect when credentials contain a character that requires URL encoding #52084
• Jersey does not use the endpoint ObjectMapper when Actuator is running on a separate port #51982
• Fractions of a second are handled incorrectly when configuring gRPC service config durations #51957
• Configuration property descriptions may be lost when building incrementally with Gradle #51925
• BasicJsonParser mishandles escaped characters in nested lists and maps #51908
• Zero week value conversion fails with 'intValue cannot be extracted from WEEKS' exception #51894
• App fails to start when using DevTools and manually configuring JDBC or R2DBC without spring-boot-jdbc or spring-boot-r2dbc #51890
• Docker Compose support incorrectly recognizes MARIADB_ALLOW_EMPTY_PASSWORD instead of MARIADB_ALLOW_EMPTY_ROOT_PASSWORD #51888
• Auto-configured Kotlinx Serialization JSON codec customization is not applied #51877
• NullPointerException can be thrown when using uber jars due to a race condition in NestedJarFileResources #51745
• DevTools does not detect a reactive web environment #51730
• spring.http.clients.cookie-handling has no effect when using a reactive client backed by an HttpComponents connector #51724
• Connection fails when rabbitmq Docker Compose service is configured to use SSL #51667
• SBOM-related manifest attributes are missing from Maven-packaged wars #51651
• When server.reactive.session.cookie.same-site is not set, session cookies have no SameSite attribute #51639
• OAuth2 resource server ignores authorities-claim-delimiter when set on its own #51630
• developmentOnly and testAndDevelopmentOnly configurations do not specify any attributes causing potential resolution problems #51623
• In a reactive web application, Cloud Foundry security integration returns a 500 rather than a 503 when the cloud controller URL is unavailable #51614
• Layer temp file is not deleted when layer creation fails #51581
• Docker Compose integration for RabbitMQ skips credential fallbacks when an environment variable has no value #51578
• Some assertion messages name the wrong parameter #51574
• OAuth2ResourceServerProperties.Jwt has a setter that does not match its getter #51562
• jarmode tools commands print stacktrace instead of an error message #51547
• Docker Compose ProcessRunner can hang or leave orphan processes #51538
• NestedByteChannel.read(ByteBuffer) incorrectly returns 0 when buffer could not be filled #51520
• Customizer null checks in HTTP client builders assert the wrong attribute #51513
• SSL host config customizations may be lost during Tomcat initialization #51511
• SQL Server Docker Compose integration may duplicate the JDBC URL's encrypt parameter #51481
• WritableJson.toByteArray() may corrupt supplementary characters #51464
• SSL host config customizations are lost when reloading SSL bundles #51457

... (truncated)

Commits

• 634e6fd Release 4.1.2
• 6b43cf1 Upgrade to Spring WS 5.0.3
• a73dfad Upgrade to Spring Security 7.1.2
• 0485f1e Upgrade to Spring RESTDocs 4.0.2
• de2c11a Upgrade to Spring Pulsar 2.0.8
• 8d0359e Upgrade to Spring LDAP 4.1.2
• f22c6e6 Upgrade to Spring Kafka 4.1.2
• ed55709 Upgrade to Spring Integration 7.1.2
• 2e88a38 Upgrade to Spring HATEOAS 3.1.3
• 0d69ce5 Upgrade to Spring gRPC 1.1.2
• Additional commits viewable in compare view

Updates tools.jackson:jackson-bom from 3.1.7 to 3.2.4

Commits

• 47303b4 [maven-release-plugin] prepare release jackson-bom-3.2.4
• cad7311 Prep for 3.2.4 release
• 2e47c28 Merge branch '3.1' into 3.2
• c41bfec Post-release dep version bump
• 86e94b2 [maven-release-plugin] prepare for next development iteration
• c70e58a [maven-release-plugin] prepare release jackson-bom-3.1.8
• 7d4ab97 Prep for 3.1.8 release
• 3244f25 Merge branch '2.x' into 3.1
• 6439613 Merge branch '2.22' into 2.x
• a7d1c9f Post-release dep version bump
• Additional commits viewable in compare view

Updates org.apache.tomcat.embed:tomcat-embed-core from 11.0.25 to 11.0.27

Updates org.apache.tomcat.embed:tomcat-embed-websocket from 11.0.25 to 11.0.27

Updates org.postgresql:postgresql from 42.7.13 to 42.7.14

Release notes

Sourced from org.postgresql:postgresql's releases.

v42.7.14

Security

This release fixes two security vulnerabilities.

requireAuth is silently not enforced when the value excludes every authentication method (GHSA-rhp9-mr79-r74h, CVE-2026-107314)

Severity: Moderate (CVSS 5.9) | Affected versions: 42.7.11 – 42.7.13

If the requireAuth connection property excluded all six authentication methods the driver knows (for example requireAuth=!password,!md5,!gss,!sspi,!scram-sha-256,!none) or contained no method at all (for example requireAuth=,), the driver applied no restriction and accepted whatever method the server asked for, including cleartext password. An attacker positioned between the application and the server could use this to request cleartext password authentication and receive the database password.

Unset values, positive lists (such as requireAuth=scram-sha-256) and partial exclusions (such as requireAuth=!password,!md5) were not affected, and neither were deployments that do not set requireAuth.

Behavior after upgrading:

• A value that excludes every method now refuses the connection with SQLState 08004 and the message Authentication method is not allowed by requireAuth (or the channel binding error when channelBinding=require is also set).
• A value that names no method is rejected as an invalid requireAuth value.

Because affected deployments had this value by mistake, and connections worked normally on affected versions, connections with such a value will fail after upgrading. Replace it with a positive list of the methods your server uses, for example requireAuth=scram-sha-256.

Independently of this fix, use sslmode=verify-full with a trusted CA so that an attacker cannot present a substitute server.

Thanks to @​manus-pi for finding and reporting this issue.

Driver stores bytes of earlier statements when it pads a value shorter than its declared length (GHSA-f64h-wr5q-3qf3, CVE-2026-107315)

Severity: Moderate (CVSS 5.3) | Affected versions: 42.7.4 – 42.7.13

When an application sent a value shorter than the length it declared, the driver padded the missing bytes with data from earlier messages on the same connection instead of zeros, and the server stored them. The stored value could contain SQL text and parameter values of earlier, unrelated statements (up to 8192 bytes, or 16320 with GSS encryption). On pooled connections, those statements could come from other requests. 42.7.3 and earlier padded with zeros.

This is reachable through the following public API when the declared length is larger than the data:

• PreparedStatement.setObject(int, ByteStreamWriter)
• CopyIn.writeToCopy(ByteStreamWriter) and CopyIn.writeToCopy(byte[], int, int)
• PGCopyOutputStream.write(byte[], int, int) (writes over 64 KiB)
• LargeObject.write(byte[], int, int)
• java.sql.Blob.setBytes(long, byte[], int, int)

Padding is now always zeros. Applications whose declared length always matches the data were not affected. Values stored by an affected version through such a call may already contain leaked data, so you may want to review affected columns. There is no connection property to disable the old behavior; the workaround on older versions is to make the declared length match the data.

Thanks to @​vlsi for finding and reporting this issue.

Full Changelog: pgjdbc/pgjdbc@REL42.7.13...REL42.7.14

Changelog

Sourced from org.postgresql:postgresql's changelog.

[42.7.14] (2026-10-07)

Security

• fix: a requireAuth value that excludes every authentication method, such as !password,!md5,!gss,!sspi,!scram-sha-256,!none, now refuses every method. A connection with such a value now fails with SQLState 08004. Before, the driver treated the value as if requireAuth were not set, and used any method the server asked for, even a cleartext password. This affects 42.7.11 through 42.7.13 GHSA-rhp9-mr79-r74h
• fix: a requireAuth value without a method in it, such as , or ,,, now fails with SQLState 22023. Before, the driver treated it as if requireAuth were not set. Commas at the very end of a value are still ignored, as in password,. This affects 42.7.11 through 42.7.13 GHSA-rhp9-mr79-r74h
• fix: a value shorter than its declared length, such as one from a ByteStreamWriter whose getLength() is larger than what writeTo() writes, is now padded with zeros. Before, the driver padded it with bytes of messages sent earlier on the same connection, so the stored value could contain SQL text and parameter values of earlier statements. This affects 42.7.4 through 42.7.13 GHSA-f64h-wr5q-3qf3

Commits

• ebdd9d0 chore: bump version to 42.7.14
• 0e764c8 test: Add additional PgBufferedOutputStream.writeZeros(...) tests
• c8998c8 fix: writeZeros() could send stale buffer contents instead of zeros
• a65ef98 fix: refuse every method when requireAuth excludes them all
• See full diff in compare view

Updates gradle-wrapper from 9.7.0 to 9.8.2

Release notes

Sourced from gradle-wrapper's releases.

9.8.2

The Gradle team is excited to announce Gradle 9.8.2.

Here are the highlights of this release:

• Java 27 support
• Maven mirror settings reuse
• Linked problem locations in build output

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle: Aman Gautam, Björn Kautler, Eng Zer Jun, Hashim Khan, Julian Krannich, KBS, Labh R Jethe, Mark Dodgson, Maxim, monkey, nataphon-ktsystems, Paul King, Qiu Tian, rg_sandesh, Roberto Perez Alcolea, Sean, Zongle Wang.

Upgrade instructions

Switch your build to use Gradle 9.8.2 by updating your wrapper:

./gradlew :wrapper --gradle-version=9.8.2 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

9.8.1

This is a patch release for Gradle 9.8.0. We recommend using 9.8.1 instead of 9.8.0.

This release addresses three high rated vulnerabilities:

... (truncated)

Commits

• 8de7bcf Speed up the AllVersionsCrossVersion flaky quarantine (#39494)
• 66805db Run all cross-version targets in flaky quarantine
• cdd4c8f Skip empty test tasks in the flaky test quarantine
• 6badb77 Split the AllVersionsCrossVersion quarantine across agents
• 1655e44 Prepare for 9.8.2 (#39492)
• 6702214 Prepare for 9.8.2
• 688c0c1 Fix false warning about unstable graph (#39479)
• 3601d4f Clarify selector reuse comments in SelectorState
• 6e836fd Fix false warning about unstable graph
• a0790e5 Fix hidden artifact cleanup pattern in CheckProject (#39451)
• Additional commits viewable in compare view

Updates com.hierynomus:sshj from 0.40.0 to 0.41.2

Release notes

Sourced from com.hierynomus:sshj's releases.

SSHJ 0.41.2

Changes

📦 Dependency Updates

• Downgrade Java compiler target version to 8 in build configuration. (#1065) @​dkocher

Full Changelog: hierynomus/sshj@v0.41.1...v0.41.2

SSHJ 0.41.1

Changes

• No changes

Full Changelog: hierynomus/sshj@v0.41.0...v0.41.1

SSHJ 0.41.0

Changes

• Fix NullPointer in DefaultConfig error logging (#1039) @​lacikaaa
• Update to most current sshj version 0.40.0 in README.adoc (#1045) @​github-pawo

🐛 Bug Fixes

• Fix: use portable EC algorithm name in ECDSAKeyFactory (#1061) @​hierynomus
• Add support for explicitly named public keys (Fixes #960) (#1060) @​hierynomus
• Fix: SFTP Directory size from server can be -1 (#1059) @​hierynomus
• Fix/opensshv1 keyfile public key init (#1057) @​hierynomus
• Fix timeout configuration bug (#1030) @​melihbirim
• Fix RemoteFileInputStream to return 0 for zero-length reads (#1049) @​arimu1
• Fix #1048: avoid ERROR logs on normal port-forward connection close (#1050) @​arimu1
• Fix loading PBES1 encrypted PKCS8 private keys (#1055) @​exceptionfactory
• Make ChannelInputStream respect connection timeout (#1034) @​jpstotz
• Ensure reset of security provider preference. (#1013) @​dkocher

✨ New Features

• Add support for explicitly named public keys (Fixes #960) (#1060) @​hierynomus
• Add FIDO2/U2F security key (sk-*) support (#1043) @​squadgazzz
• Add SSH agent authentication support (#1042) @​squadgazzz
• ProxyCommand support (Issue 970) (#971) @​knoxg

📦 Dependency Updates

• Upgrade to Java 17 and gradle 9 (#1044) @​hierynomus
• Update groovy and spock-core so tests can run in java 21 (#1040) @​alexandrejbr
• Update build.gradle (bouncycastle version) (#1035) @​github-pawo

🔨 Improvements

... (truncated)

Commits

• 6fad160 Merge pull request #1065 from iterate-ch/issues/1064-java8
• dacefc5 Downgrade Java compiler target version to 8 in build configuration.
• d0ecfd2 >Update sonatype release
• 243f339 Merge pull request #1062 from hierynomus/feat/rfc-8308
• f986c90 Fix flaky ConcurrentModificationException in StrictKeyExchangeTest
• b5aa3fb Strengthen integration test to prove server-sig-algs reordering
• d1574ab Feat: parse SSH_MSG_EXT_INFO server-sig-algs (RFC 8308)
• 2bb495a Merge pull request #1061 from hierynomus/fix/ecdsa-keyfactory-algorithm-name
• 175bf73 Merge branch 'master' into fix/ecdsa-keyfactory-algorithm-name
• da89216 Merge pull request #1060 from hierynomus/fix/explicit-pubkey
• Additional commits viewable in compare view

Updates com.github.mwiede:jsch from 2.28.6 to 2.28.8

Release notes

Sourced from com.github.mwiede:jsch's releases.

jsch-2.28.8

What's Changed

• 2.28.8 changes by @​norrisjeremy in mwiede/jsch#1134
  • #1133: bounds check incoming SSH_FXP_DATA responses.
  • #1133: cap length of incoming HTTP status response lines.
  • #1127: expand on previous SftpATTRS bounds checks to properly close SSH_FX_READDIR handles.
  • #1139: add bounds checks when parsing prompts from SSH_MSG_USERAUTH_INFO_REQUEST messages.
  • #1127 & #1139: expand upon previous bounds checks to account for arithmetic overflow.
• Support wildcard host certificate principals by @​tc-tlv in mwiede/jsch#1108
• Expose local SFTP window/packet size setters as public by @​courville in mwiede/jsch#1145

Dependency Updates

• Bump github/codeql-action/init from 4.37.7 to 4.37.8 by @​dependabot[bot] in mwiede/jsch#1136
• Bump github/codeql-action/analyze from 4.37.7 to 4.37.9 by @​dependabot[bot] in mwiede/jsch#1141
• Bump junixsocket.version from 2.11.0 to 2.11.1 by @​dependabot[bot] in mwiede/jsch#1140
• Bump org.slf4j:slf4j-api from 2.0.18 to 2.0.19 by @​dependabot[bot] in mwiede/jsch#1148
• Bump org.codehaus.mojo:build-helper-maven-plugin from 3.6.1 to 3.6.2 by @​dependabot[bot] in mwiede/jsch#1152
• Bump org.codehaus.mojo:templating-maven-plugin from 3.1.0 to 3.1.1 by @​dependabot[bot] in mwiede/jsch#1153
• Bump org.slf4j:slf4j-api from 2.0.19 to 2.0.20 by @​dependabot[bot] in mwiede/jsch#1171
• Bump net.codecrete.windows-api:windowsapi-maven-plugin from 0.8.6 to 0.8.7 by @​dependabot[bot] in mwiede/jsch#1170
• Bump biz.aQute.bnd:bnd-maven-plugin from 7.3.0 to 7.4.0 by @​dependabot[bot] in mwiede/jsch#1135
• Bump surefire.version from 3.5.6 to 3.6.0 by @​dependabot[bot] in mwiede/jsch#1146
• Bump org.apache.maven.plugins:maven-compiler-plugin from 3.15.0 to 3.16.0 by @​dependabot[bot] in mwiede/jsch#1147
• Bump org.bouncycastle:bcprov-jdk18on from 1.85.2 to 1.86 by @​dependabot[bot] in mwiede/jsch#1150
• Bump org.apache.maven.plugins:maven-install-plugin from 3.1.4 to 3.2.0 by @​dependabot[bot] in mwiede/jsch#1151
• Bump org.apache.maven.plugins:maven-deploy-plugin from 3.1.4 to 3.2.0 by @​dependabot[bot] in mwiede/jsch#1154
• Bump actions/setup-java from 5.7.0 to 6.0.1 by @​dependabot[bot] in mwiede/jsch#1156
• Bump org.apache.maven:apache-maven from 3.9.16 to 3.10.0 by @​dependabot[bot] in mwiede/jsch#1176
• Bump github/codeql-action/analyze from 4.37.9 to 4.38.2 by @​dependabot[bot] in mwiede/jsch#1174
• Bump github/codeql-action/autobuild from 4.37.7 to 4.38.2 by @​dependabot[bot] in mwiede/jsch#1173
• Bump github/codeql-action/init from 4.37.8 to 4.38.2 by @​dependabot[bot] in mwiede/jsch#1172
• Bump de.thetaphi:forbiddenapis from 3.10 to 3.11 by @​dependabot[bot] in mwiede/jsch#1169

New Contributors

• @​tc-tlv made their first contribution in mwiede/jsch#1108
• @​courville made their first contribution in mwiede/jsch#1145

Full Changelog: mwiede/jsch@jsch-2.28.7...jsch-2.28.8

jsch-2.28.7

What's Changed

• Add Session accessors for the negotiated algorithms by @​fornwall in mwiede/jsch#1101
• As per RFC 8268, enforce range checks on DH public keys. by @​norrisjeremy in mwiede/jsch#1105
• add bounds checks while parsing K_S. by @​norrisjeremy in mwiede/jsch#1106
• • #1127: add bounds checks when parsing SFTP vendor-specific extensions.
  • Treat the reserved field in certs as an opaque byte array instead of a String. by @​norrisjeremy in mwiede/jsch#1128

Depenency Updates

• Bump org.codehaus.mojo:flatten-maven-plugin from 1.7.3 to 1.8.0 by @​dependabot[bot] in mwiede/jsch#1103
• Bump org.apache.maven.plugins:maven-toolchains-plugin from 3.2.0 to 3.3.0 by @​dependabot[bot] in mwiede/jsch#1102
• Bump commons-codec:commons-codec from 1.22.0 to 1.22.1 by @​dependabot[bot] in mwiede/jsch#1109
• Bump org.cyclonedx:cyclonedx-maven-plugin from 2.9.2 to 2.9.3 by @​dependabot[bot] in mwiede/jsch#1110

... (truncated)

Commits

• 36c4d26 [maven-release-plugin] prepare release jsch-2.28.8
• cd4e924 chore: downgrade maven version after publishing problems
• 53f016a Expose local SFTP window/packet size setters as public (#1145)
• 898c6c2 Run tests on Java 27.
• cc7e534 Update to Maven 3.10.0.
• 660f42d Follow OpenSSH behavior and restrict maximum number of KDF rounds.
• 9b13e61 Follow OpenSSH behavior and use Huffman coding for zlib compression.
• 780e57e #1127 & #1139: expand upon previous bounds checks to account for arithmetic o...
• f94e745 #1139: add bounds checks when parsing prompts from SSH_MSG_USERAUTH_INFO_REQU...
• d2a3658 #1127: expand on previous SftpATTRS bounds checks to properly close SSH_FX_RE...
• Additional commits viewable in compare view

Updates org.eclipse.jgit:org.eclipse.jgit from 7.7.1.202607240634-r to 7.8.0.202609011348-r

Commits

• f386af5 JGit v7.8.0.202609011348-r
• 1c5afcc Merge branch 'master' into stable-7.8
• db8cba3 IndexDiffFilter: Don't drop untracked folders unrelated to a tracked change
• 92c2312 Fix NPE in close() with nothing to fetch
• 14d0c55 Merge "DfsPackFile: honor to conf to read changedPathFilters"
• 79f0c50 Merge branch 'master' into stable-7.8
• a34a12e Merge branch 'stable-7.7'
• c062a12 Merge branch 'stable-7.6' into stable-7.7
• 989a5c4 Merge branch 'stable-7.5' into stable-7.6
• 1fbb306 Merge branch 'stable-7.4' into stable-7.5
• Additional commits viewable in compare view

Updates org.bouncycastle:bcpkix-jdk18on from 1.85 to 1.86

Changelog

Sourced from org.bouncycastle:bcpkix-jdk18on's changelog.

Bouncy Castle Crypto Package - Release Notes

1.0 Introduction

The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. The package is organised so that it contains a light-weight API suitable for use in any environment (including the J2ME) with the additional infrastructure to conform the algorithms to the JCE framework.

2.0 Release History

2.1.1 Version

Release: 1.87
Date: 2026, TBD

2.1.2 Defects Fixed

• X500Name.equals compared two names that are equal but not byte-identical - the same RDNs in another order, or in another string type - by searching the second name for each RDN of the first and canonicalising both values on every candidate comparison, so the comparison was quadratic in the number of RDNs, and CMSSignedData.getSignerInfos(), the CMSEnvelopedData, CMSAuthEnvelopedData and CMSEnvelopedDataParser constructors, TimeStampToken, the S/MIME classes built on them and X509CertificateHolderSelector.match() all compare names taken from the message before anything in it is verified: a 1.1 MB signed or enveloped message carrying two 40,000 RDN issuer names took about 90 seconds of CPU to parse. The signer and recipient stores also indexed their entries in a HashMap keyed on the signer or recipient id, whose hash code is easy to make collide, so a message with 16,000 signers or recipients chosen to collide took several seconds to index. AbstractX500NameStyle.areEqual now compares the RDNs positionally and otherwise sorts the canonical form of each RDN once and compares the two multisets, so a comparison is n log n in the number of RDNs, the two stores now scan their entries on lookup instead of indexing them, and the selector checks the serial number before the issuer name.
• The hash code of an ASN.1 object is a short fold over its content octets that a sender can make collide at will, and several tables built while a message is parsed were keyed on one: the extension table behind Extensions, so every certificate, CRL, OCSP and timestamp request parse, the deprecated X509Extensions, ExtendedKeyUsage, the CMS AttributeTable built from a SignerInfo's signed and unsigned attributes (the unsigned ones lying outside the signature), the EST CSRAttributesResponse index, and the Set of digest AlgorithmIdentifiers that the CMSSignedDataParser constructor and CMSSignedData.getDigestAlgorithmIDs() build from the SignedData digestAlgorithms field. With every key sharing one hash code each insert scanned all those before it, so a 6 MB certificate or message holding 65,000 such entries took about 35 seconds of CPU to parse and the parser's digest algorithm set about 140 seconds. Those tables are now ordered maps keyed on the OID's string form and the digest algorithm sets are ordered on the identifier's DER encoding, so each is n log n in the number of entries whatever their hash codes. AttributeTable.add() and remove() also no longer share a multi-valued entry's Vector with the table they were derived from.
• CMSSignedData digested the encapsulated or detached content once for every signer it verified, so a message carrying many SignerInfos over a large content cost their product in digesting before any signature was checked, where CMSSignedDataParser digests once per algorithm named in the digestAlgorithms field. The signers of a CMSSignedData now share the content digests computed under each digest algorithm identifier, so signers using the same algorithm digest the content once. The new org.bouncycastle.cms.max_digest_algorithms property bounds the number of distinct digest algorithms either class will compute over one message's content, each algorithm past the limit raising a CMSException; it is unlimited unless set.
• The verify side of the ML-DSA-CALCULATE-MU signature service, and MLDSASigner.verifyMu beneath it, compared the supplied mu with a value derived from the key's tr and the context alone, never absorbing the message passed to update(), so a correct mu was accepted only for an empty message and rejected for every other, while the sign side of the same service computed mu correctly. The comparison also finalised the engine's shared digest, so an ordinary verifySignature on the same MLDSASigner afterwards failed for a valid signature, and a mu of the wrong length escaped Signature.verify() as an unchecked DataLengthException. verifyMu now derives the expected mu from the message digest exactly as generateMu does and compares in constant time, the signer stays usable afterwards, the service answers a wrong-length mu with a SignatureException, and the contract - the verify side accepts exactly the mu the sign side returns for the same key, context and data - is now in the javadoc of both.
• The SM2 key pair generator of the BC provider, KeyPairGenerator.getInstance("SM2", "BC"), was built on the generic EC key pair generator rather than the lightweight SM2KeyPairGenerator the 1.73 release notes described, so it could draw a private key of n - 1, which Section 6.1 of GB/T 32918.1 excludes and which the SM2 signer rejects. It now uses SM2KeyPairGenerator and draws from [1, n - 2].
• ESTResponse added each header line of an EST server's response to its header table by copying that header's value array, so a response repeating one header many times was quadratic to parse - about 7 seconds of CPU per megabyte of header lines - and a read limit set through JsseESTServiceBuilder.withReadLimit() only applied once the header block had been read. The values of each header are now collected once, and the header block counts against the read limit of the source.
• The C509 encoding of an RFC 6955 proof-of-possession value (the sa-ecdhPop signature algorithms, values 14 to 16 of the C509 Signature Algorithms Registry) copied the DER DhSigStatic into the signature value byte string, where Section 4.2 of draft-ietf-cose-cbor-encoded-cert-21 defines the value as the bare hashValue when the DhSigStatic names no issuer and serial number and as the [issuer, certificateSerialNumber, hashValue] array when it does. The converter now produces both forms from the DER and reconstructs the DER from either; previously the array form was rejected outright and the byte-string form reconstructed a signature value four bytes short of the DER it came from, so a type 3 request carrying one could not verify. The privateKeyPossessionStatement certification request attribute (RFC 9883, Section 4.3.3 of the draft) was carried in the generic ~oid form on conversion and refused on reconstruction; it is now converted to and from its int-coded [issuer, certificateSerialNumber, cert] form, with an embedded signature certificate re-encoded as a type 3 C509 certificate. The certificate, certification request and template vectors of draft-ietf-cose-c509-test-vectors-02 now drive the util and pkix test suites.
• The DANE SMIMEA support in org.bouncycastle.cert.dane had three defects. JndiDANEFetcherFactory, when asked for every entry under a bare domain name, removed the first and last characters of the owner name the JNDI DNS provider reports for each listed record, assuming a quoted name; the provider returns the name unquoted with a trailing root dot, so the first hex digit of the hash label was lost and the lookup that followed could never find the record. It now removes only the root dot. DANEEntryStore kept one entry per owner name, so an address with more than one SMIMEA record (a signing and an encryption certificate, say) only ever showed its last; every entry is now kept. DANEEntrySelectorFactory split an address at its first '@', mis-handling a quoted local-part containing one, and threw StringIndexOutOfBoundsException rather than DANEException for an address with none; it now splits at the last '@', removes enclosing quotes and backslash quoting from the local-part before hashing as RFC 8162 sec. 3 describes, and rejects an address with no '@'. The DANEEntry(String, byte[]) constructor also now rejects, with an IOException, a record whose flags do not describe a full certificate entry rather than parsing whatever follows the flags as a certificate.
• TimeStampToken accepted a token whose signing-time signed attribute disagreed with the genTime in its TSTInfo. Both are the TSA's statement of when the token was produced, and the disagreement is what distinguishes an RFC 3161 token from a signature a TSA has put over a supplied TSTInfo through another service using the same key, such as a legacy countersignature endpoint, which some TSAs still offer. The constructor now rejects a token whose signing-time, when present, is further from genTime than the token's accuracy plus one minute; the check can be switched off with the org.bouncycastle.tsp.allow_inconsistent_signing_time property. TimeStampTokenGenerator now sets a signing-time attribute from the genTime it is given rather than the clock, so its tokens are consistent whatever genTime is passed.
• TimeStampToken.validate() accepted a token whose message imprint was calculated with MD5, for which collisions can be computed, and TSPAlgorithms.ALLOWED, the set the request side is typically checked against, included MD5. MD5 has been removed from TSPAlgorithms.ALLOWED, and validate() now rejects a token whose imprint algorithm is not in it (failure code badAlg). The new TSPAlgorithms.LEGACY is ALLOWED plus MD5; validate(SignerInformationVerifier, Set) takes the set of acceptable imprint algorithms, and the org.bouncycastle.tsp.allowed_imprint_algorithms property, a comma separated list of digest names or OIDs, replaces ALLOWED as the default for validate(SignerInformationVerifier). TSPAlgorithms.ALLOWED and LEGACY are now unmodifiable.
• CRL-based revocation checking (the PKIX CertPathValidator and the pkix X509RevocationChecker) tracked a CRL entry's reasonCode in the same field as its own status markers and did not range-check it, so a CRL entry whose reasonCode was outside the RFC 5280 sec. 5.3.1 set was mishandled: 11 left the certificate unrevoked, other out-of-range values threw an unchecked exception out of validation. The revocation date and the reason code are now kept separately; an undefined reasonCode is processed as unspecified and reported as "(unknown code: N)".
• OERDefinition.enumItem(label, value) discarded the explicit enumerand value: Builder.enumValue() set it on the builder it had just copied and returned the copy without it, so every item was numbered by its position in the definition instead. The value is now kept, and the items without one are numbered as X.680 sec. 20.3 and 20.6 specify: a root item takes the successive integers from 0, skipping any explicit root number, and an extension item takes the smallest value not defined in the root and greater than every preceding extension item (the old loop restarted its count after an explicit number, so an explicit 0 followed by an unnumbered item was a duplicate). The three ETSI TS 102 941 response-code definitions that use explicit values give "ok" the value 0 at position 0, so their encodings are unchanged.
• OERInputStream read the two length-prefixed INTEGER forms and BIT STRING with Streams.readFully and did not check its best-effort return, so a stream that ended inside the value decoded the zero-padded buffer as a value rather than failing. Every length-driven read in the decoder now goes through Streams.readLenBytesFully, which fails with EOFException at the real end of input and, for a long length, does not allocate the full array until the stream has delivered a fair part of it - so a hostile length that is within the decoder's allocation cap, or a cap a caller has raised, cannot drive a large allocation from a short input.
• The OER codec gave a signed INTEGER whose upper bound is exactly the maximum of a fixed-size word the next word up: X.696 sec. 10.4 a)-d) make both bounds inclusive, but the upper-bound comparison was strict, so INTEGER (-128..127) was a two-octet word rather than one, and likewise at the 16-, 32- and 64-bit boundaries. The two signed ranges shipped with the library, NinetyDegreeInt and OneEightyDegreeInt, lie inside the four-octet word and are unaffected.
• The ETSI TS 102 941 response code wrappers Authorizat...

  Description has been truncated