[vaadin-bot]

Same notes as added to #9739 (25.3) and #9740 (25.2).

• opentelemetry-api 1.64.0 / 1.65.0 / 1.66.0: also cover CVE-2026-118259 (GHSA-ccrj-gw8r-854m, affects <= 1.66.0). Real opentelemetry-java CVE in W3CTraceContextPropagator.extract(), but the artifact only reaches the SBOM through selenium-remote-driver under TestBench, a test only http client, so inbound headers are never extracted.

• picomatch 4.0.7 (CVE-2026-112366): build time only via vite / rolldown / vite-plugin-checker, globs come from developer config. No fixed release yet.

• lerc 3.0.0 (CVE-2026-10758): only reached via ol -> geotiff to decode LERC compressed GeoTIFF; Vaadin Map has no GeoTIFF source.

• highcharts 12.2.0 (5 CVEs): fixed in Vaadin Charts by fix: skip unsupported values in chart options web-components#12886 without bumping Highcharts (announced as CVE-2026-107588). Scanners flag 12.2.0 by version only; feat: upgrade Highcharts to 12.6.2 web-components#13289 (Highcharts 12.6.2) clears the alert.

Guava is real and fixed by a bump in vaadin/hilla#6734, not by a note.

🤖 Generated with Claude Code

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:maven/com.google.guava/guava@33.6.0-jre [CVE-2026-102554] (osv-bomber,osv-scan)
    ·

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:maven/io.opentelemetry/opentelemetry-api@1.66.0 [CVE-2026-118259, CVE-2026-54285] (osv-bomber,osv-scan,owasp)
    👌 FP: the CVE targets the OpenTelemetry JavaScript SDK (@opentelemetry/core < 2.8.0, CPE target_sw=node.js, GHSA-8988-4f7v-96qf). The CPE is matched against the Java opentelemetry-api artifact, which is a separate codebase and not affected. CVE-2026-118259 (GHSA-ccrj-gw8r-854m, fixed in 1.67.0) is a ReDoS in W3CTraceContextPropagator.extract() parsing inbound tracestate headers. Not affected: the artifact reaches the sbom only through selenium-remote-driver under vaadin-testbench, a test only dependency acting as an http client, so untrusted inbound headers are never extracted. Upgrade once selenium ships 1.67.0+.
    ·
    · cpe:2.3:a:opentelemetry:opentelemetry::::::node.js::*
  • Vulnerabilities in: pkg:npm/highcharts@12.2.0 [CVE-2026-118246, CVE-2026-118251, CVE-2026-118244, CVE-2026-116796, CVE-2026-118250] (osv-bomber,oss-bomber,osv-scan)
    👌 Fixed in Vaadin Charts without bumping the bundled Highcharts (announced as CVE-2026-107588): fix: skip unsupported values in chart options web-components#12886, cherry-picked to 25.1, 25.2 and 25.3, ignores reserved segments in series.keys and point option names, credits links without a supported URL scheme and event attribute names in style options applied as SVG attributes, and parses text markup in an inert document when the default parser fails. Scanners keep flagging 12.2.0 by version only. The bump to Highcharts 12.6.2 (feat: upgrade Highcharts to 12.6.2 web-components#13289) replaces these patches with the upstream fixes and clears the alert.
    ·
  • Vulnerabilities in: pkg:npm/picomatch@4.0.7 [CVE-2026-112366] (oss-bomber)
    👌 Build-time only: picomatch is pulled in by vite, rolldown and vite-plugin-checker and is not shipped in production bundles. The ReDoS requires an attacker supplied extglob pattern such as +(*), while the globs come from the developer's own build configuration. No fixed version is published on npm yet (4.0.7 is latest); upgrade once available.
    ·
  • Vulnerabilities in: pkg:npm/lerc@3.0.0 [CVE-2026-10758] (oss-bomber)
    👌 Not affected: lerc arrives through ol -> geotiff and is only used to decode LERC compressed GeoTIFF imagery. Vaadin Map does not expose a GeoTIFF source, so the decoder is never on the execution path; worst case impact would be a crashed browser tab. vulnerable_code_not_in_execute_path.
    ·
  • Vulnerabilities in: pkg:maven/me.friwi/jcef-api@jcef-ca49ada%2Bcef-135.0.20%2Bge7de5c3%2Bchromium-135.0.7049.85 [CVE-2024-21639, CVE-2024-21640, CVE-2024-9410] (owasp)
    👌 Wait for the update from the jcefmaven community. Meanwhile the swing-kit is supposed to be used with fixed websites and not to browse the internet, we have a check for that, so the only possible attacker would be the same person that created the swing application, aka our customer devs. so this vulnerability is not classified by us as critical issue
    · cpe:2.3:a:chromiumembedded:chromium_embedded_framework::::::::
    · cpe:2.3:a:ada:ada::::::::
  • Vulnerabilities in: pkg:maven/com.vaadin/vaadin-swing-kit-flow@3.0.1 [CVE-2021-33604] (owasp)
    👌 false report: this CVE is targeting Vaadin version prior 20, swing-kit-flow is using vaadin 24+ version, the related issue has been fixed.
    · cpe:2.3:a:vaadin:flow-server::::::::
    · cpe:2.3:a:vaadin:vaadin::::::::

• 📔 No Core License Issues

• 📔 No License Issues

• 🟠 Changes in 25.4-SNAPSHOT since V25.4.0-alpha4

  • 10 packages modified (10 external, 0 vaadin)
  • 569 packages same (343 external, 226 vaadin)

[Click for more Details]