Skip to content

Dependabot: Bump the maven-patch-and-minor group with 3 updates - #38

Merged
github-actions[bot] merged 1 commit into
master-dependency-updatefrom
dependabot/maven/master-dependency-update/maven-patch-and-minor-ec05890d87
Oct 26, 2026
Merged

Dependabot: Bump the maven-patch-and-minor group with 3 updates#38
github-actions[bot] merged 1 commit into
master-dependency-updatefrom
dependabot/maven/master-dependency-update/maven-patch-and-minor-ec05890d87

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 26, 2026

Copy link
Copy Markdown
Contributor

Bumps the maven-patch-and-minor group with 3 updates: org.springframework.boot:spring-boot-starter-parent, org.codehaus.mojo:build-helper-maven-plugin and org.postgresql:postgresql.

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

Release notes

Sourced from org.springframework.boot:spring-boot-starter-parent'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 org.codehaus.mojo:build-helper-maven-plugin from 3.6.1 to 3.6.2

Release notes

Sourced from org.codehaus.mojo:build-helper-maven-plugin's releases.

3.6.2

🐛 Bug Fixes

👻 Maintenance

  • Remove redundant maven-resolver-api dependency and ignore Resolver/SLF4J 2.x in Dependabot (#248) @​slachiewicz

📦 Dependency updates

Commits
  • 813bc7d [maven-release-plugin] prepare release 3.6.2
  • 07d9109 Remove redundant maven-resolver-api and ignore Resolver/SLF4J 2.x in Dependabot
  • 9abd552 Bump org.codehaus.plexus:plexus-utils from 4.0.3 to 4.1.0
  • 3c15526 Bump apache/maven-gh-actions-shared/.github/workflows/release-drafter.yml
  • 3b1f104 Bump org.codehaus.mojo:mojo-parent from 96 to 97
  • 1749855 Bump apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml
  • 5230041 Bump org.codehaus.plexus:plexus-utils from 4.0.2 to 4.0.3
  • c0e9375 Delete .github/release-drafter.yml
  • 84a839e Bump org.codehaus.mojo:mojo-parent from 95 to 96
  • a85c668 Replace raw NPEx with customized exception message
  • Additional commits viewable in compare view

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.

Changelog

Notable changes since version 42.0.0, read the complete History of Changes.

The format is based on Keep a Changelog.

[Unreleased]

Fixed

  • fix: PGStream.skip no longer loops forever when the connection ends while the driver is discarding bytes, and no longer mistakes a stream that skips nothing for one that has ended. InputStream.skip may return zero with more data still coming, which a stream supplied through the socketFactory property is free to do; the driver now reads a byte in that case and treats only -1 as the end [PR #4358](pgjdbc/pgjdbc#4358)
  • fix: LargeObjectManager operations now work inside an active XA transaction. Since 42.7.13 an XA branch keeps the caller's autoCommit=true, and the guard rejected large objects as if the connection were idle. It now checks the server transaction state (getTransactionState()) instead of autoCommit, so a genuine auto-commit connection with no open transaction is still refused [Issue #4309](pgjdbc/pgjdbc#4309) [PR #4310](pgjdbc/pgjdbc#4310)
  • fix: batch update counts are no longer secured as committed inside an XA transaction. BatchResultHandler treated per-statement progress as durable whenever autoCommit=true, but an XA branch keeps autoCommit=true while the transaction is open, so a batch that flushed mid-way and then failed could report rolled-back statements as succeeded. Progress is now secured only when no server transaction is open [Issue #4309](pgjdbc/pgjdbc#4309) [PR #4311](pgjdbc/pgjdbc#4311)

Changed

  • fix: backend message lengths are checked before anything is sized from them. Each length is checked against the message layout and a limit for its type, the lengths inside DataRow and FunctionCallResponse are checked against the message, and the NegotiateProtocolVersion option count is bounded. A hostile or out of sync backend could previously force an allocation of up to two gigabytes with a five byte header [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: the read buffer is limited to 32 MiB and grows once per request rather than once per socket read. It previously doubled on every read while a large request was outstanding, so a peer that declared a large length and sent it slowly grew the buffer until the doubling past 1 GiB overflowed to a negative size [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: a zero-length CopyData body is accepted. It is valid on the wire and was previously rejected by an assertion, so it failed only on JVMs started with -ea [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: GSS packet lengths are bounded. The encrypted transport is limited to a 16380 byte payload and the handshake to a 65532 byte token, matching PQ_GSS_MAX_PACKET_SIZE and PQ_GSS_AUTH_BUFFER_SIZE [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: a connection whose stream has been refused is no longer reusable. Any refused length or count marks the stream broken, so Connection.isClosed() reports it closed and a pool that tests on borrow discards it. The socket is dropped with SO_LINGER 0 [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: a protocol violation before authentication is reported as PSQLException with SQLState 08P01 rather than as a plain I/O error, and is no longer retried under sslMode=allow or sslMode=prefer [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: the counts inside RowDescription, ParameterDescription, CopyInResponse and CopyOutResponse are checked against the declared message length. A RowDescription claiming more fields than its length can hold previously read its field descriptions out of the messages that followed it [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: the driver checks that each backend message was consumed exactly before reading the next message type, so a reader that stops short of its declared length is refused rather than misreading what follows [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: the authentication loop, the GSS encryption handshake and the GSS authentication handshake each stop after 64 round trips. A zero-length GSS token is a valid continuation, so a server could previously keep a client exchanging tokens forever before any credentials were exchanged [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: ErrorResponse before authentication is limited to 30000 bytes rather than 32 MiB, matching libpq's limit for messages outside VALID_LONG_MESSAGE_TYPE, and a C string inside a declared message is no longer scanned past the end of that message. Both were allocations an unauthenticated peer could cause [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: an ErrorResponse or NoticeResponse longer than 32 MiB is truncated to that size rather than refused. The body past the limit is drained and the shortened message is delivered, so the connection stays usable [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: the read buffer returns to its initial size once the message that grew it is drained, so a connection no longer retains 32 MiB after one large error [Issue #4015](pgjdbc/pgjdbc#4015)
  • fix: exceeding maxResultBuffer closes the connection. The row is not read past the limit, so the connection cannot continue, and it is now dropped where the limit is exceeded rather than refused as a protocol violation at the next message. The error reported is the limit alone, with SQLState 08S01 as before [Issue #4015](pgjdbc/pgjdbc#4015)

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
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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Dependabot: Bump the maven-patch-and-minor group with 3 updates
6daf64e 
Bumps the maven-patch-and-minor group with 3 updates: [org.springframework.boot:spring-boot-starter-parent](https://github.com/spring-projects/spring-boot), [org.codehaus.mojo:build-helper-maven-plugin](https://github.com/mojohaus/build-helper-maven-plugin) and [org.postgresql:postgresql](https://github.com/pgjdbc/pgjdbc).


Updates `org.springframework.boot:spring-boot-starter-parent` from 4.1.1 to 4.1.2
- [Release notes](https://github.com/spring-projects/spring-boot/releases)
- [Commits](spring-projects/spring-boot@v4.1.1...v4.1.2)

Updates `org.codehaus.mojo:build-helper-maven-plugin` from 3.6.1 to 3.6.2
- [Release notes](https://github.com/mojohaus/build-helper-maven-plugin/releases)
- [Commits](mojohaus/build-helper-maven-plugin@3.6.1...3.6.2)

Updates `org.postgresql:postgresql` from 42.7.13 to 42.7.14
- [Release notes](https://github.com/pgjdbc/pgjdbc/releases)
- [Changelog](https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md)
- [Commits](pgjdbc/pgjdbc@REL42.7.13...REL42.7.14)

---
updated-dependencies:
- dependency-name: org.springframework.boot:spring-boot-starter-parent
  dependency-version: 4.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-patch-and-minor
- dependency-name: org.codehaus.mojo:build-helper-maven-plugin
  dependency-version: 3.6.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: maven-patch-and-minor
- dependency-name: org.postgresql:postgresql
  dependency-version: 42.7.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-patch-and-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Oct 26, 2026
@github-actions
github-actions Bot merged commit 58c7f66 into master-dependency-update Oct 26, 2026
1 check passed
@dependabot
dependabot Bot deleted the dependabot/maven/master-dependency-update/maven-patch-and-minor-ec05890d87 branch October 26, 2026 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file java Pull requests that update java code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants