Update all dependencies - #70
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Dependency ReviewThe following issues were found:
License Issues.github/workflows/ktlint.yml
pom.xml
OpenSSF Scorecard
Scanned Files
|
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
March 24, 2026 09:05
205da9e to
130d056
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
March 31, 2026 20:47
0c7e11d to
ae7c54e
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
April 12, 2026 00:37
c27aca0 to
bb5227c
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
April 14, 2026 13:39
bb5227c to
447bd77
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
April 28, 2026 23:16
75cc4f1 to
6f2211d
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
May 12, 2026 17:30
1baf893 to
9c3371c
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
May 21, 2026 10:59
eeeab84 to
273b751
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
June 4, 2026 16:26
e51830f to
67eba4e
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
June 10, 2026 19:34
a88be56 to
ddffb01
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
June 18, 2026 19:37
ddffb01 to
d1af237
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
June 30, 2026 15:48
d1af237 to
177c25d
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
July 10, 2026 16:42
e9b8120 to
b1f6928
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
July 23, 2026 16:48
6250190 to
186d3fb
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
August 2, 2026 01:06
8e18774 to
cadb3bc
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 6, 2026 13:08
cadb3bc to
52c1013
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 13, 2026 13:44
52c1013 to
da7c4a1
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 20, 2026 13:54
da7c4a1 to
e32d3a1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v6→v742.7.10→42.7.125.22.0→5.23.03.0.2→3.1.011.34→11.38.212.0.3→13.3.03.5.0→3.7.13.6.2→3.6.37.20.0→7.24.04.0.3→4.1.1pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS
CVE-2026-42198 / GHSA-98qh-xjc8-98pq
More information
Details
Summary
pgjdbc is vulnerable to a client-side denial of service during SCRAM-SHA-256 authentication.
Impact
A malicious server can instruct the driver to perform SCRAM authentication with a very large iteration count.
With a large enough value, the client spends an unbounded amount of CPU time inside PBKDF2 before authentication can fail.
A single attempt ties up a CPU core. Repeated or concurrent attempts exhaust client CPU and can wedge connection pools.
In affected versions,
loginTimeoutdid not fully mitigate this problem. WhenloginTimeoutexpired, the caller could stop waiting, but the worker thread performing the connection attempt could continue running and burning CPU inside the SCRAM PBKDF2 computation.This issue affects availability. It does not provide authentication bypass, privilege escalation, or direct password disclosure.
A user is vulnerable when all of the following are true:
server-first-message.In practice, that can happen in these situations:
/etc/hosts, environment variables, or similar indirectionsslmodelower thanverify-full, or trusting a CA that signs hosts outside the operator's control)The issue is more damaging when the application uses connection retries, many parallel connection attempts, or
loginTimeoutand assumes the timeout fully stops the work.Patches
The patch introduces a new connection property,
scramMaxIterations, with a default of 100K. The client now rejects SCRAM server messages that advertise more PBKDF2 iterations than the configured cap before starting the PBKDF2 computation begins.Workarounds
Until a patched version of pgjdbc is deployed, the following measures reduce exposure:
Only connect to trusted PostgreSQL servers whose identity is verified.
Connect only to trusted PostgreSQL servers, and verify server identity with TLS using sslmode=verify-full and a trusted CA.
TLS without certificate and hostname verification is not sufficient as an active network attacker can still impersonate the server.
Do not rely on
loginTimeoutas a complete mitigation on unpatched versions.On affected versions,
loginTimeoutcan stop the waiting caller while the worker thread continues spending CPU.Avoid SCRAM on untrusted or interceptable connection paths.
For those paths, use an authentication method that does not let the server choose a SCRAM PBKDF2 iteration count.
Reduce blast radius operationally.
Limit parallel connection attempts, add retry backoff, isolate connection establishment in a separate worker or process when possible, and apply CPU or container limits where appropriate.
On trusted servers you control, keep SCRAM iteration counts at ordinary values.
This does not defend against an attacker-controlled server, but it avoids unnecessary client cost when talking to legitimate servers.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
PostgreSQL JDBC Driver: Silent channel-binding authentication downgrade via unsupported certificate algorithms
CVE-2026-54291 / GHSA-j92g-9f8w-j867
More information
Details
Impact
channelBinding=requireconnections can be silently downgraded fromSCRAM-SHA-256-PLUS(with channel binding) to plainSCRAM-SHA-256(without it), losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection triggers the downgrade with a certificate whose signature algorithm has notls-server-end-pointchannel-binding hash. Examples areEd25519,Ed448, and post-quantum algorithms.Two issues combine in releases 42.7.4 through 42.7.11:
com.ongres.scram:scram-client(3.1 or 3.2) returns an empty byte array instead of failing when it cannot derive the binding hash for such a certificate. This is the library issue tracked as GHSA-p9jg-fcr6-3mhf.channelBinding=requirewhere it matters.ScramAuthenticatorchecks only that the server advertised a-PLUSmechanism; it neither rejects the empty binding nor checks that the negotiated mechanism uses channel binding. The connection therefore downgrades silently, and would do so even against a fixedscram-client, because the missing enforcement is in pgJDBC's own code.Only connections that set
channelBinding=requireare affected. Under the defaultpreferpolicy, and underallowordisable, falling back to plain SCRAM is the documented behaviour. Releases before 42.7.4 are unaffected, because they do not support channel binding.Patches
Fixed in pgJDBC 42.7.12. pgJDBC now enforces channel binding in its own code, independently of the
scram-clientversion:channelBinding=require, it fails the connection when no channel-binding data can be extracted from the server certificate, instead of passing an empty value to the SCRAM client. The error names the certificate signature algorithm.-PLUSmechanism) wheneverchannelBinding=requireis set, regardless of how negotiation resolved.Upgrade to 42.7.12 or later.
Workarounds
No pgJDBC setting restores channel-binding enforcement on an affected release; upgrading is the fix.
If you cannot upgrade immediately, verify the server certificate at the TLS layer so that a man-in-the-middle cannot present a substitute certificate. Set
sslmode=verify-fullwith a truststore that contains only your server's CA. This defence is independent of channel binding and blocks the same attacker. Connections that rely onchannelBinding=requirein place of certificate verification have no equivalent workaround and should upgrade.References
com.ongres.scram:scram-clientissue (root cause of the empty channel-binding value).scram-client3.3 release (library fix): https://github.com/ongres/scram/releases/tag/3.3Severity
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
actions/checkout (actions/checkout)
v7.0.1Compare Source
v7.0.0Compare Source
v7Compare Source
v6.1.0Compare Source
v6.0.3Compare Source
v6.0.2Compare Source
v6.0.1Compare Source
pgjdbc/pgjdbc (org.postgresql:postgresql)
v42.7.12Security
Under
channelBinding=require, the driver silently downgraded fromSCRAM-SHA-256-PLUS(with channel binding) to plainSCRAM-SHA-256(without it) when the server presented a certificate whose signature algorithm has notls-server-end-pointchannel-binding hash (e.g.Ed25519, Ed448, or post-quantum algorithms). An attacker who can intercept the TLS connection could exploit this to strip channel-binding protection.The fix enforces channel binding in the driver's own code: it now fails the connection when no binding data can be extracted, and verifies the negotiated mechanism uses channel binding (
-PLUS) whenrequireis set.Only connections that set
channelBinding=requireare affected. The defaultpreferpolicy and releases before 42.7.4 (which introduced channel-binding support) are unaffected.See the Security Advisory for more detail.
The following CVE-2026-54291 has been issued.
v42.7.11Security
pgjdbc was vulnerable to a client-side denial of service in SCRAM-SHA-256 authentication, where a malicious or compromised PostgreSQL server could specify an extremely large PBKDF2 iteration count, causing the client to consume unbounded CPU and potentially exhaust connection pools. The fix introduces a new scramMaxIterations connection property (defaulting to 100,000) to cap iteration counts before computation begins.
See the Security Advisory for more detail.
The following CVE-2026-42198 has been issued.
Added
Changed
Fixed
mockito/mockito (org.mockito:mockito-core)
v5.23.0Compare Source
NOTE: Breaking change for Android
The
mockito-androidartifact has a breaking change: tests now require a device or emulator based on API 28+ (Android P). This is to enable new support for mocking Kotlin classes. See #3788 for more details.Changelog generated by Shipkit Changelog Gradle Plugin
5.23.0
Mockito.when@Nullable(#3503)springdoc/springdoc-openapi (org.springdoc:springdoc-openapi-starter-webmvc-ui)
v3.1.0Compare Source
Added
nullablefor Kotlin propertiesChanged
Fixed
swagger-configSNAKE_CASE: some Java record fields remain camelCaseWebPropertiesandWebMvcPropertiesoptional inSwaggerConfignest()predicate across all routes innestPageschema property orderParameterObjectproperty applied toPathVariablewith the same name, even in unrelated endpointsMapnot allowed in JSONv3.0.3: springdoc-openapi v3.0.3 released!Compare Source
Added
nullable: truefor Kotlin nullable types in schema properties@Rangeconstraint validation annotationLocalDateChanged
@ConditionalOnClass(HateoasProperties.class)inSpringDocHateoasConfigurationwindow.location.pathnamefor MCP UIFixed
Directionenum: fixed visibility scope of group order so thatsetGroupsOrdermethod can be usedPropertyResolverUtilsretains aJsonNodewhen reading anExtensionPropertyannotationJsonViewcontext when resolvingPage<T>schemaNew Contributors
Full Changelog: springdoc/springdoc-openapi@v3.0.2...v3.0.3
connect2id/oauth-2.0-sdk-with-openid-connect-extensions (com.nimbusds:oauth2-oidc-sdk)
v11.38.2Compare Source
v11.38.1Compare Source
v11.38Compare Source
v11.37.2Compare Source
v11.37.1Compare Source
v11.37Compare Source
v11.36Compare Source
v11.35Compare Source
gantsign/ktlint-maven-plugin (com.github.gantsign.maven:ktlint-maven-plugin)
v3.7.1Compare Source
Changes:
v3.7.0Compare Source
Enhancement:
v3.6.0Compare Source
Enhancement:
Other changes:
openapitools/openapi-generator (org.openapitools:openapi-generator-maven-plugin)
v7.24.0: releasedCompare Source
v7.24.0 stable release (breaking changes with fallbacks) comes with 170+ enhancements and bug fixes.
Below are the highlights of the changes. For a full list of changes, please refer to the "Pull Request" tab.
General
asciidoc
avro
C++
C#
Crystal
Dart
Go
Java
Julia
Kotlin
openapi, openapi-yaml
PHP
Python
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.
This change is