Skip to content

chore(deps): bump springKafka2 from 2.8.11 to 4.1.2 - #6629

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/springKafka2-4.1.2
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/springKafka2-4.1.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 17, 2026

Copy link
Copy Markdown
Contributor

Bumps springKafka2 from 2.8.11 to 4.1.2.
Updates org.springframework.kafka:spring-kafka from 2.8.11 to 4.1.2

Release notes

Sourced from org.springframework.kafka:spring-kafka's releases.

v4.1.2

🐞 Bug Fixes

  • KafkaTemplate.receive() returns a record at a different offset when the requested offset is missing #4830
  • GH-4823: Keep partition pause across child containers #4828
  • KafkaAdmin reports topic config alteration failures as 'Failed to obtain topic descriptions' #4826
  • ContainerGroupSequencer does not disable autoStartup of containers with an idleEventInterval #4824
  • DefaultErrorHandler ignores backOffFunction when the default BackOff has no retries #4818
  • Flaky BatchListenerConversionTests.conversionError() #4817
  • Share container isInExpectedState() ignores a consumer thread that exited on an error #4814
  • ReplyingKafkaTemplate reply future times out instead of failing when the send fails #4811
  • AbstractConsumerSeekAware.onPartitionsRevoked() removes other consumers' callbacks #4808
  • RoutingKafkaTemplate.partitionsFor() throws UnsupportedOperationException #4805
  • Share consumer ack timeout warning ignores renew() #4804
  • Lambda or method-reference Converter beans break @KafkaListener startup #4802
  • CommonMixedErrorHandler does not delegate onPartitionsAssigned(), losing records during batch retry #4797
  • Support the two-arg deserialize in DelegatingByTopicDeserializer #4794
  • Deserialization exception headers mapped outbound with Kafka 4.4 clients #4775
  • Cooperative rebalance can leave the partitions a consumer retains permanently unconsumed (async listener) #4772
  • Retry topics use BackOff.STOP (-1) as a delay when the BackOff has its own limit #4770
  • AbstractConsumerSeekAware retains callback mappings after unregister #4767
  • Mixed and delegating error handlers discard remaining batch records when seekAfterError is false #4765
  • ExponentialBackOffWithMaxRetries(0) still retries once #4760
  • Make ExceptionMatcher cache thread-safe #4757
  • acknowledge() after a partial batch ack commits only the next record #4734
  • ConcurrentMessageListenerContainer does not report partition pause requests from child containers #4730
  • Apply the bootstrap servers supplier in DefaultShareConsumerFactory #4699
  • Suspend @KafkaListener: consumer permanently stops fetching partitions it retains across a rebalance #4696
  • Async listener reply success path never reports failures to the receiver Observation #4686
  • Pending consumer wakeup aborts the next offset commit, which is then skipped #4683
  • Drain queued share acknowledgments on stop #4680
  • Copy the type resolver in copyWithType #4666
  • ShareKafkaMessageListenerContainer NPEs at start() when built from a topic pattern or partition list #4664
  • Do not validate a null deserialized value #4656
  • ShareConsumerAcknowledgment state can regress from a terminal type to RENEW #4646
  • Multi-value header mapping loses values on inbound when a JSON type header is present #4644
  • ReplyingKafkaOperations sendAndReceive overloads expose incorrect nullability for replyTimeout and returnType #4642
  • DelegatingByTypeSerializer assignable mode can select a more general delegate due to a non-transitive comparator #4633
  • Share containers ignore ContainerProperties.clientId #4627
  • ShareKafkaListenerContainerFactory.createContainer(String...) does not apply factory configuration #4617
  • Recovering Streams exception handlers throw when there is no source record #4611
  • Assert messages in setTopicPartitions and setDefaultReplyTimeout name the wrong property #4609
  • Kafka listener with autoStartup=false is unconditionally started on ApplicationContext.restart() (alwaysStartAfterRefresh=true ignores autoStartup after first refresh) #4608
  • Close the default delegate in DelegatingByTopicSerialization #4589
  • DelegatingByTypeSerializer does not close its delegates #4579

📔 Documentation

  • Fix stale API names in the reference docs #4748
  • Misleading autoStartDltHandler property/documentation for @RetryableTopic in tests #4701

... (truncated)

Commits
  • 4504070 Release 4.1.2
  • d404c95 Prepare release 4.1.2
  • 4bf9c62 Update release train dependency versions
  • c8426de Set internal version to 4.1.2-INTERNAL-SNAPSHOT
  • b42c929 Fix ShareKafkaMessageListenerContainerUnitTests on few CPUs
  • e4cd101 GH-4784: Reject batch nack before a partial ack
  • fa3810a Bump org.hibernate.validator:hibernate-validator (#4832)
  • a044f57 GH-4792: Receive only the record at the offset
  • 3b2f729 Fix flaky ShareKafkaMessageListenerContainerUnitTests
  • 3f78996 GH-4823: Keep partition pause across child containers
  • Additional commits viewable in compare view

Updates org.springframework.kafka:spring-kafka-test from 2.8.11 to 4.1.2

Release notes

Sourced from org.springframework.kafka:spring-kafka-test's releases.

v4.1.2

🐞 Bug Fixes

  • KafkaTemplate.receive() returns a record at a different offset when the requested offset is missing #4830
  • GH-4823: Keep partition pause across child containers #4828
  • KafkaAdmin reports topic config alteration failures as 'Failed to obtain topic descriptions' #4826
  • ContainerGroupSequencer does not disable autoStartup of containers with an idleEventInterval #4824
  • DefaultErrorHandler ignores backOffFunction when the default BackOff has no retries #4818
  • Flaky BatchListenerConversionTests.conversionError() #4817
  • Share container isInExpectedState() ignores a consumer thread that exited on an error #4814
  • ReplyingKafkaTemplate reply future times out instead of failing when the send fails #4811
  • AbstractConsumerSeekAware.onPartitionsRevoked() removes other consumers' callbacks #4808
  • RoutingKafkaTemplate.partitionsFor() throws UnsupportedOperationException #4805
  • Share consumer ack timeout warning ignores renew() #4804
  • Lambda or method-reference Converter beans break @KafkaListener startup #4802
  • CommonMixedErrorHandler does not delegate onPartitionsAssigned(), losing records during batch retry #4797
  • Support the two-arg deserialize in DelegatingByTopicDeserializer #4794
  • Deserialization exception headers mapped outbound with Kafka 4.4 clients #4775
  • Cooperative rebalance can leave the partitions a consumer retains permanently unconsumed (async listener) #4772
  • Retry topics use BackOff.STOP (-1) as a delay when the BackOff has its own limit #4770
  • AbstractConsumerSeekAware retains callback mappings after unregister #4767
  • Mixed and delegating error handlers discard remaining batch records when seekAfterError is false #4765
  • ExponentialBackOffWithMaxRetries(0) still retries once #4760
  • Make ExceptionMatcher cache thread-safe #4757
  • acknowledge() after a partial batch ack commits only the next record #4734
  • ConcurrentMessageListenerContainer does not report partition pause requests from child containers #4730
  • Apply the bootstrap servers supplier in DefaultShareConsumerFactory #4699
  • Suspend @KafkaListener: consumer permanently stops fetching partitions it retains across a rebalance #4696
  • Async listener reply success path never reports failures to the receiver Observation #4686
  • Pending consumer wakeup aborts the next offset commit, which is then skipped #4683
  • Drain queued share acknowledgments on stop #4680
  • Copy the type resolver in copyWithType #4666
  • ShareKafkaMessageListenerContainer NPEs at start() when built from a topic pattern or partition list #4664
  • Do not validate a null deserialized value #4656
  • ShareConsumerAcknowledgment state can regress from a terminal type to RENEW #4646
  • Multi-value header mapping loses values on inbound when a JSON type header is present #4644
  • ReplyingKafkaOperations sendAndReceive overloads expose incorrect nullability for replyTimeout and returnType #4642
  • DelegatingByTypeSerializer assignable mode can select a more general delegate due to a non-transitive comparator #4633
  • Share containers ignore ContainerProperties.clientId #4627
  • ShareKafkaListenerContainerFactory.createContainer(String...) does not apply factory configuration #4617
  • Recovering Streams exception handlers throw when there is no source record #4611
  • Assert messages in setTopicPartitions and setDefaultReplyTimeout name the wrong property #4609
  • Kafka listener with autoStartup=false is unconditionally started on ApplicationContext.restart() (alwaysStartAfterRefresh=true ignores autoStartup after first refresh) #4608
  • Close the default delegate in DelegatingByTopicSerialization #4589
  • DelegatingByTypeSerializer does not close its delegates #4579

📔 Documentation

  • Fix stale API names in the reference docs #4748
  • Misleading autoStartDltHandler property/documentation for @RetryableTopic in tests #4701

... (truncated)

Commits
  • 4504070 Release 4.1.2
  • d404c95 Prepare release 4.1.2
  • 4bf9c62 Update release train dependency versions
  • c8426de Set internal version to 4.1.2-INTERNAL-SNAPSHOT
  • b42c929 Fix ShareKafkaMessageListenerContainerUnitTests on few CPUs
  • e4cd101 GH-4784: Reject batch nack before a partial ack
  • fa3810a Bump org.hibernate.validator:hibernate-validator (#4832)
  • a044f57 GH-4792: Receive only the record at the offset
  • 3b2f729 Fix flaky ShareKafkaMessageListenerContainerUnitTests
  • 3f78996 GH-4823: Keep partition pause across child containers
  • 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps `springKafka2` from 2.8.11 to 4.1.2.

Updates `org.springframework.kafka:spring-kafka` from 2.8.11 to 4.1.2
- [Release notes](https://github.com/spring-projects/spring-kafka/releases)
- [Commits](spring-projects/spring-kafka@v2.8.11...v4.1.2)

Updates `org.springframework.kafka:spring-kafka-test` from 2.8.11 to 4.1.2
- [Release notes](https://github.com/spring-projects/spring-kafka/releases)
- [Commits](spring-projects/spring-kafka@v2.8.11...v4.1.2)

---
updated-dependencies:
- dependency-name: org.springframework.kafka:spring-kafka
  dependency-version: 4.1.2
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.springframework.kafka:spring-kafka-test
  dependency-version: 4.1.2
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested review from a team and adinauer as code owners November 17, 2026 04:15
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file Java SDK labels Nov 17, 2026
@dependabot
dependabot Bot requested review from markushi and runningcode and removed request for a team November 17, 2026 04:15
@socket-security

Copy link
Copy Markdown

Warning

Socket is a tool Sentry Security team deployed to defend against supply chain attack. Please provide any feedback you have in #discuss-security slack channel ❤️

Priority Alert  (click "▶" to expand/collapse) Action
Critical priority
Critical CVE: Apache Tomcat - Security constraints not correctly applied in maven org.apache.tomcat.embed:tomcat-embed-core

CVE: GHSA-5m62-pw8w-7w9f Apache Tomcat - Security constraints not correctly applied (CRITICAL)

Affected versions: < 9.0.118; >= 10.1.0-M1 < 10.1.55; >= 11.0.0-M1 < 11.0.22

Patched version: 9.0.118

From: gradle/libs.versions.toml → maven/org.apache.tomcat.embed/tomcat-embed-jasper@9.0.108 → maven/org.apache.tomcat.embed/tomcat-embed-core@9.0.108

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.apache.tomcat.embed/tomcat-embed-core@9.0.108. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: Apache Tomcat - Digest authenticator will authenticate any unknown user in maven org.apache.tomcat.embed:tomcat-embed-core

CVE: GHSA-h6fc-48rj-7qqh Apache Tomcat - Digest authenticator will authenticate any unknown user (CRITICAL)

Affected versions: < 9.0.118; >= 10.1.0-M1 < 10.1.55; >= 11.0.0-M1 < 11.0.22

Patched version: 9.0.118

From: gradle/libs.versions.toml → maven/org.apache.tomcat.embed/tomcat-embed-jasper@9.0.108 → maven/org.apache.tomcat.embed/tomcat-embed-core@9.0.108

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.apache.tomcat.embed/tomcat-embed-core@9.0.108. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: Apache Tomcat - HTTP/2 request headers not validated in maven org.apache.tomcat.embed:tomcat-embed-core

CVE: GHSA-r29c-68gh-xp6x Apache Tomcat - HTTP/2 request headers not validated (CRITICAL)

Affected versions: >= 8.5.0 < 9.0.118; >= 10.1.0-M1 < 10.1.55; >= 11.0.0-M1 < 11.0.22

Patched version: 9.0.118

From: gradle/libs.versions.toml → maven/org.apache.tomcat.embed/tomcat-embed-jasper@9.0.108 → maven/org.apache.tomcat.embed/tomcat-embed-core@9.0.108

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.apache.tomcat.embed/tomcat-embed-core@9.0.108. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: Apache Tomcat - Security constraints not correctly applied in maven org.apache.tomcat:tomcat-catalina

CVE: GHSA-5m62-pw8w-7w9f Apache Tomcat - Security constraints not correctly applied (CRITICAL)

Affected versions: < 9.0.118; >= 10.1.0-M1 < 10.1.55; >= 11.0.0-M1 < 11.0.22

Patched version: 9.0.118

From: gradle/libs.versions.toml → maven/org.apache.tomcat/tomcat-catalina@9.0.108

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.apache.tomcat/tomcat-catalina@9.0.108. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: Apache Tomcat - Digest authenticator will authenticate any unknown user in maven org.apache.tomcat:tomcat-catalina

CVE: GHSA-h6fc-48rj-7qqh Apache Tomcat - Digest authenticator will authenticate any unknown user (CRITICAL)

Affected versions: < 9.0.118; >= 10.1.0-M1 < 10.1.55; >= 11.0.0-M1 < 11.0.22

Patched version: 9.0.118

From: gradle/libs.versions.toml → maven/org.apache.tomcat/tomcat-catalina@9.0.108

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.apache.tomcat/tomcat-catalina@9.0.108. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: Apache Tomcat - HTTP/2 request headers not validated in maven org.apache.tomcat:tomcat-coyote

CVE: GHSA-r29c-68gh-xp6x Apache Tomcat - HTTP/2 request headers not validated (CRITICAL)

Affected versions: >= 8.5.0 < 9.0.118; >= 10.1.0-M1 < 10.1.55; >= 11.0.0-M1 < 11.0.22

Patched version: 9.0.118

From: gradle/libs.versions.toml → maven/org.apache.tomcat/tomcat-catalina@9.0.108 → maven/org.apache.tomcat/tomcat-coyote@9.0.108

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.apache.tomcat/tomcat-coyote@9.0.108. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn

View full report

@github-actions github-actions Bot added the risk: high PR risk score: high label Nov 17, 2026
@sentry

sentry Bot commented Nov 17, 2026

Copy link
Copy Markdown

📲 Install Builds

Android

🔗 App Name App ID Version Configuration
SDK Size io.sentry.tests.size 8.64.0 (1) release

⚙️ sentry-android Build Distribution Settings

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 623b84f. Configure here.

Comment thread gradle/libs.versions.toml
springKafka2 = "2.8.11"
springKafka3 = "3.3.5"
springKafka2 = "4.1.2"
springKafka3 = "4.1.2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spring Kafka pins skip generations

High Severity

springKafka2 and springKafka3 now both pin Spring Kafka 4.1.2, which needs Spring Framework 7 and Kafka clients 4.x. Those keys compile and test the Boot 2 (sentry-spring) and Boot 3 (sentry-spring-jakarta) matrices, which still run Spring 5/6 and Kafka 3. Boot 4 already uses BOM-managed spring-kafka4.

Fix in Cursor Fix in Web

Triggered by project rule: PR Review Guidelines for Cursor Bugbot

Reviewed by Cursor Bugbot for commit 623b84f. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file Java SDK risk: high PR risk score: high

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant