[pushkala-datastax]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• pulsar-io/dynamodb/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-21761837	740	com.amazonaws:dynamodb-streams-kinesis-adapter: 1.5.1 -> 2.0.0 Major version upgrade No Path Found Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

Vulnerabilities that could not be fixed

• Upgrade:
  • Could not upgrade com.fasterxml.jackson.core:jackson-databind@2.16.0 to com.fasterxml.jackson.core:jackson-databind@2.18.12; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/com/fasterxml/jackson/jackson-bom/2.16.0/jackson-bom-2.16.0.pom
• Could not upgrade com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.16.0 to com.fasterxml.jackson.dataformat:jackson-dataformat-cbor@2.18.12; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/com/fasterxml/jackson/jackson-bom/2.16.0/jackson-bom-2.16.0.pom
• Could not upgrade com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.16.0 to com.fasterxml.jackson.dataformat:jackson-dataformat-yaml@2.18.12; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/com/fasterxml/jackson/jackson-bom/2.16.0/jackson-bom-2.16.0.pom

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Deserialization of Untrusted Data

[pushkala-datastax]

This set of upgrades includes a high-risk major version change for the DynamoDB Streams Kinesis Adapter and medium-risk minor updates for Jackson libraries that introduce stricter validation.

Top Impact Upgrade

com.amazonaws:dynamodb-streams-kinesis-adapter 1.5.1 → 2.0.0 (HIGH RISK)

This is a major version upgrade that requires significant code and dependency changes. Version 2.x of the adapter was released to support version 2.x of the AWS SDK for Java and version 3.x of the Amazon Kinesis Client Library (KCL).

Breaking Changes:

• Migration from AWS SDK v1 to v2: The library no longer depends on the AWS SDK for Java v1. Your application code must be migrated to use the AWS SDK for Java v2 APIs, which involve different package names, client builders, and request/response objects.
• Migration from KCL 1.x to KCL 3.x: The adapter is now built for KCL 3.x. This requires updating how the KCL worker and scheduler are initialized and configured in your application.

Recommendation: This upgrade cannot be merged without a dedicated migration effort. Developers must refactor the application to adopt the AWS SDK for Java v2 and the new KCL 3.x interfaces. Review the official AWS documentation for migrating from KCL 1.x to 3.x.

Other Upgrades

com.fasterxml.jackson.* 2.16.0 → 2.18.12 (MEDIUM RISK)

This upgrade across jackson-databind, jackson-dataformat-cbor, and jackson-dataformat-yaml introduces stricter validation rules, primarily to address security vulnerabilities.

Behavioral Changes:

• Stricter Polymorphic Type Validation: Versions in the 2.18.x range include fixes for multiple CVEs (like CVE-2026-54512 and CVE-2026-54513) that tighten the rules for deserializing polymorphic types, especially with nested generics and arrays. Deserialization that previously worked might now fail if it relies on insecure type conversions.
• Stricter Number Deserialization: Version 2.17 introduced stricter validation for stringified numbers to prevent issues like coercion of NaN to BigDecimal.

Recommendation: While there are no direct API removals, these behavioral changes warrant a medium risk assessment. After upgrading, thoroughly test all deserialization paths, paying special attention to any use of polymorphic type handling (@JsonTypeInfo or enableDefaultTyping) to ensure the stricter security checks do not break legitimate use cases.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.