Update versions.postgresql [SECURITY]#70
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Dependency ReviewThe following issues were found:
License Issuespom.xml
OpenSSF Scorecard
Scanned Files
|
205da9e to
130d056
Compare
0c7e11d to
ae7c54e
Compare
c27aca0 to
bb5227c
Compare
bb5227c to
447bd77
Compare
75cc4f1 to
6f2211d
Compare
1baf893 to
9c3371c
Compare
eeeab84 to
273b751
Compare
e51830f to
67eba4e
Compare
e79ea0c to
a88be56
Compare
a88be56 to
ddffb01
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:
42.7.10→42.7.115.22.0→5.23.03.0.2→3.0.311.34→11.37.212.0.3→12.8.13.5.0→3.7.13.6.2→3.6.37.20.0→7.23.04.0.3→4.1.0pgjdbc: 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).
Release Notes
pgjdbc/pgjdbc (org.postgresql:postgresql)
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.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.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.23.0: releasedCompare Source
v7.23.0 stable release (breaking changes with fallbacks) comes with 170+ enhancements and bug fixes.
This release comes with 2 breaking changes (with fallback):
Below are the highlights of the changes. For a full list of changes, please refer to the "Pull Request" tab.
General
C#
Dart
Go
Java
Kotlin
Python
PHP
PowerShell
Rust
Scala
Swift
TypeScript
v7.22.0: releasedCompare Source
v7.22.0 stable release comes with 150+ 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
C#
Crystal
Dart
Go
Java
Kotlin
PHP
PowerShell
Python
Rust
Scala
Swift
TypeScript
v7.21.0: releasedCompare Source
v7.21.0 stable release (breaking changes with fallbacks) comes with 190+ enhancements and bug fixes.
This release comes with 3 breaking changes (with fallback):
Below are the highlights of the changes. For a full list of changes, please refer to the "Pull Request" tab.
General
C
C#
C++
Dart
Go
Java
JavaScript
Kotlin
Configuration
📅 Schedule: (UTC)
🚦 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