[dependabot]

Bumps the maven-deps group with 3 updates in the / directory: org.apache.httpcomponents.client5:httpclient5, org.postgresql:postgresql and se.bjurr.gitchangelog:git-changelog-maven-plugin.

Updates org.apache.httpcomponents.client5:httpclient5 from 5.6.4 to 5.6.5

Changelog

Sourced from org.apache.httpcomponents.client5:httpclient5's changelog.

Release 5.6.5

This maintenance release fixes several defects found since the previous release including the defect in the async Brotli decompression code that can cause the message exchange to hang indefinitely. It also upgrades HttpCore to version 5.4.4.

Change Log

• Upgraded HttpCore to version 5.4.4. Contributed by Oleg Kalnichevski

• HTTPCLIENT-2433: Prevent concurrent HTTP/2 request body replay. Contributed by Matthias Kurz <m.kurz at irregular.at>

• HTTPCLIENT-2432: Fixed connection-pool leak in ResponseEntityProxy#cleanup() when runtime #disconnectEndpoint throws an exception (#883). Contributed by Victor Alekseev

• Decode punycode public suffixes in PublicSuffixMatcher#verify (#876). Contributed by Javid Khan

• Fixed Brotli decompression hang with large input buffers. Contributed by Arturo Bernal

• HTTP cache to treat malformed delta-seconds as absent. Contributed by Arturo Bernal Javid Khan

• Bug-fix: ResponseCachingPolicy incorrectly applies neverCache1_1ResponsesWithQueryString config parameter. This config parameter and related functionality will be deprecated in the next feature release and removed in the future. Contributed by Oleg Kalnichevski

• Removed invalid request version check from ResponseCachingPolicy. Contributed by Oleg Kalnichevski

• Fixed resource leaking on error in AsyncCachingExec Contributed by Jeremie Bolduc <16137441+Jouramie at users.noreply.github.com>

Commits

• e6970b4 HttpClient 5.6.5 release
• d0ff6ec Updated release notes for HttpClient 5.6.5 release
• 03a2abc Upgraded HttpCore to version 5.4.4
• 7ed9d66 HTTPCLIENT-2433: Prevent concurrent HTTP/2 request body replay
• bd278a6 Improved connection expiry and eviction example
• 02f11eb HTTPCLIENT-2432: fix connection-pool leak in ResponseEntityProxy.cleanup() wh...
• 8e45f17 decode punycode public suffixes in PublicSuffixMatcher.verify (#876)
• 6d8319a Fix Brotli decompression hang with large input buffers
• 908ccc1 treat malformed delta-seconds as absent in deltaSeconds
• 815043a Moved timeout and stale connection related integration tests into separate gr...
• 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

Updates se.bjurr.gitchangelog:git-changelog-maven-plugin from 2.2.11 to 2.5.4

Release notes

Sourced from se.bjurr.gitchangelog:git-changelog-maven-plugin's releases.

v2.5.4

🐛 Bug Fixes

• bump (#90) (ff665 Tomas Bjerre)

🧰 Other changes

Revert "chore(deps): update dependency maven to v3.10.0 (#89)"

• This reverts commit d4953675ac44ef76cf43b6fae6e2fd9eac81c75d.

2c613 Tomas Bjerre 2026-10-03 18:25:26

v2.5.3

🐛 Bug Fixes

• ci pin Maven wrapper back to 3.9.16 (again) (4fa64 Tomas Bjerre)

📦 Dependency updates

• update dependency maven to v3.10.0 (#89) (d4953 renovate[bot])

v2.5.2

🐛 Bug Fixes

• ci pin Maven wrapper back to 3.9.16 (b11c4 Tomas Bjerre)

📦 Dependency updates

• update dependency maven to v3.10.0 (#88) (b49d2 renovate[bot])

v2.5.1

🐛 Bug Fixes

• update to git-changelog-lib 5.0.0 (#87) (a802c Tomas Bjerre)

📦 Dependency updates

• update dependency maven to v3.10.0 (#86) (b56cb renovate[bot])
• update dependency se.bjurr.gitchangelog:git-changelog-maven-plugin to v2.5.0 (#85) (b3066 renovate[bot])

v2.5.0

🚀 Features

... (truncated)

Changelog

Sourced from se.bjurr.gitchangelog:git-changelog-maven-plugin's changelog.

2.5.4 (2026-10-03)

Bug Fixes

• bump (#90) (ff665 Tomas Bjerre)

Other changes

2.5.0 (2026-09-17)

Features

• add commitCount and jiraRestBasePath parameters (#80) (424f3 Tomas Bjerre)
• expose pathFilter on the semantic-version goal for monorepos (#75) (9f203 Tomas Bjerre)
• expose jiraIssueAdditionalFields mojo parameter (#72) (4c7d7 Tomas Bjerre)

Other changes

Update dependency se.bjurr.maven:bjurr-maven-plugin-parent to v1.2.2 (#84)

• Co-authored-by: renovate[bot] <29139614+renovate[bot]@​users.noreply.github.com>

d893f renovate[bot] 2026-09-17 03:57:13

Update dependency se.bjurr.maven:bjurr-maven-plugin-parent to v1.2.0 (#83)

• Co-authored-by: renovate[bot] <29139614+renovate[bot]@​users.noreply.github.com>

ae71d renovate[bot] 2026-09-16 22:51:06

Update dependency se.bjurr.gitchangelog:git-changelog-maven-plugin to v2.4.0 (#82)

• Co-authored-by: renovate[bot] <29139614+renovate[bot]@​users.noreply.github.com>

bfb98 renovate[bot] 2026-09-16 17:31:54

Update dependency se.bjurr.gitchangelog:git-changelog-lib to v3.2.0 (#81)

• Co-authored-by: renovate[bot] <29139614+renovate[bot]@​users.noreply.github.com>

231f1 renovate[bot] 2026-09-16 17:31:27

Update dependency org.openjdk.nashorn:nashorn-core to v15.7 (#77)

• Co-authored-by: renovate[bot] <29139614+renovate[bot]@​users.noreply.github.com>

c046b renovate[bot] 2026-09-16 16:06:52

Update dependency org.apache.maven.plugins:maven-plugin-plugin to v3.16.0 (#76)

... (truncated)

Commits

• ff66544 fix: bump (#90)
• 2c6133a Revert "chore(deps): update dependency maven to v3.10.0 (#89)"
• d495367 chore(deps): update dependency maven to v3.10.0 (#89)
• 4fa64f3 fix(ci): pin Maven wrapper back to 3.9.16 (again)
• b49d22f chore(deps): update dependency maven to v3.10.0 (#88)
• b11c4e4 fix(ci): pin Maven wrapper back to 3.9.16
• a802ca1 fix: update to git-changelog-lib 5.0.0 (#87)
• b56cbb6 chore(deps): update dependency maven to v3.10.0 (#86)
• b3066f0 chore(deps): update dependency se.bjurr.gitchangelog:git-changelog-maven-plug...
• c43c2a7 chore(changelog): updating changelog
• Additional commits viewable 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