chore(security): bump deps to address reported CVEs#27994
Conversation
- log4j 2.25.3 -> 2.25.4 (CVE-2026-34477/34478/34480) - jsonschema2pojo 1.2.2 -> 1.3.0 (CVE-2025-3588) - netty-bom 4.1.132 -> 4.1.133 (netty-codec/transport GHSAs) - azure-identity 1.14.0 -> 1.15.2 in openmetadata-service to align with parent dependencyManagement
There was a problem hiding this comment.
Pull request overview
Updates Maven dependency versions to remediate security findings reported by SCA/AWS Inspector, primarily by bumping centrally-managed versions in the parent POM and aligning a service-module override.
Changes:
- Bumped
jsonschema2pojoto1.3.0. - Bumped
log4jto2.25.4. - Bumped
io.netty:netty-bomto4.1.133.Final. - Bumped
com.azure:azure-identity(service module property) to1.15.2.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| pom.xml | Updates shared dependency version properties and the imported Netty BOM version used across modules. |
| openmetadata-service/pom.xml | Updates the service module’s azure-identity version property to the patched release. |
| <dropwizard.swagger.version>4.0.5-1</dropwizard.swagger.version> | ||
| <awssdk.version>2.30.19</awssdk.version> | ||
| <azure-identity.version>1.14.0</azure-identity.version> | ||
| <azure-identity.version>1.15.2</azure-identity.version> |
1.3.0 dropped its declared dep on plexus-utils, breaking the maven-plugin at runtime with NoClassDefFoundError on org/codehaus/plexus/util/DirectoryScanner. 1.3.1 restores it. 1.3.3 has a separate regression (IndexOutOfBoundsException in ValidRule), so 1.3.1 is the right pin.
Code Review ✅ ApprovedUpdates Log4j, jsonschema2pojo, netty-bom, and azure-identity versions to patch identified CVEs. No issues found. OptionsDisplay: compact → Showing less information. Comment with these commands to change:
Was this helpful? React with 👍 / 👎 | Gitar |
|
🟡 Playwright Results — all passed (9 flaky)✅ 4019 passed · ❌ 0 failed · 🟡 9 flaky · ⏭️ 86 skipped
🟡 9 flaky test(s) (passed on retry)
How to debug locally# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip # view trace |
* chore(security): bump deps to address reported CVEs - log4j 2.25.3 -> 2.25.4 (CVE-2026-34477/34478/34480) - jsonschema2pojo 1.2.2 -> 1.3.0 (CVE-2025-3588) - netty-bom 4.1.132 -> 4.1.133 (netty-codec/transport GHSAs) - azure-identity 1.14.0 -> 1.15.2 in openmetadata-service to align with parent dependencyManagement * fix: bump jsonschema2pojo to 1.3.1 to fix maven-plugin classpath 1.3.0 dropped its declared dep on plexus-utils, breaking the maven-plugin at runtime with NoClassDefFoundError on org/codehaus/plexus/util/DirectoryScanner. 1.3.1 restores it. 1.3.3 has a separate regression (IndexOutOfBoundsException in ValidRule), so 1.3.1 is the right pin. (cherry picked from commit 9956592)



Describe your changes:
Bumps a few Maven dependencies to address vulnerabilities reported by our SCA / AWS Inspector scans.
log4jjsonschema2pojonetty-bomazure-identity(inopenmetadata-service)dependencyManagement; covers CVE-2024-35255Other CVEs in the report (jetty 12.1.7, bouncycastle 1.84, logback 1.5.25, angus-mail 2.0.4) are already at fix versions on
main.net.i2p.crypto:eddsaandorg.eclipse.jgitare not in our Maven dependency tree (verified viamvn dependency:treeacross all 16 modules) — they originate elsewhere (likely the Airflow base image or a stale scanned image) and cannot be addressed frompom.xml.lcms2is an Alpine OS package handled by the Dockerapk upgradestep.Type of change:
Tests:
Manual testing performed
mvn dependency:tree -pl openmetadata-service -amand confirmed the resolved versions arelog4j-core:2.25.4,jsonschema2pojo-core:1.3.0,netty-codec:4.1.133.Final,azure-identity:1.15.2.UI screen recording / screenshots:
Not applicable.
Checklist:
Summary by Gitar
jsonschema2pojo.versionfrom1.3.0to1.3.1inpom.xmlto resolve classpath issues with the maven-plugin.This will update automatically on new commits.