[manolo]

Follow-up to #9799.

What was wrong. The cve-status check compared a snapshot build as the bare line, so 25.3-SNAPSHOT counted as 25.3, which is before any patch. A cve-status verdict such as "fixed from 25.3.5" (>=25.3.5,<25.4) therefore did not apply, and the risk verdict for <25.3.5 matched instead. That is why the backport's SBOM run, https://github.com/vaadin/platform/actions/runs/41637731164, went red on Quill CVE-2025-15056.

The fix. A snapshot is now judged as prev.lastPatch, the newest release of its line. The script already computes it for the dependency comparison:

• 25.3-SNAPSHOT is judged as 25.3.5;
• 25.4-SNAPSHOT is judged as 25.4.0-alpha4.

When a line has no release yet, the build version is used, as before.

On main this changes nothing today: 25.4.0-alpha4 still carries the Quill risk, which is correct.

Related to #9804

🤖 Generated with Claude Code

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:javascript/quill@2.0.3 [CVE-2025-15056] (owasp)
    · cpe:2.3:a:slab:quill:2.0.3:::::node.js::

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:maven/io.opentelemetry/opentelemetry-api@1.62.0 [CVE-2026-118259, CVE-2026-54285] (osv-bomber,osv-scan,owasp)
    👌 [cve-status] Your scanner has matched the wrong product. The CPE it used, opentelemetry:opentelemetry, names the project rather than a package and carries the platform each record is about: CVE-2026-54285 is an advisory of opentelemetry-js on node.js, and the other four are advisories of the Go implementation. None is about a Java artifact, but the Java libraries share the product name, so each lands on every io.opentelemetry jar your application resolves. The range is open because the claim is about which implementation the records name, which no Java version changes. Nothing to upgrade for these. The parser is in the jar and nothing in a Vaadin application hands it an incoming header. From 25.3, opentelemetry-api 1.62.0 arrives through TestBench, whose Selenium client only adds trace context to the requests it sends, and Observability Kit no longer uses OpenTelemetry or an agent. The advisory needs incoming tracestate headers to reach W3CTraceContextPropagator.extract, which happens only if you add tracing of your own: Spring Boot OpenTelemetry tracing, the OpenTelemetry Java agent, or code that extracts trace context from requests.
    ·
    · 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/org.jetbrains.kotlin/kotlin-stdlib@2.3.21 [CVE-2026-53914] (owasp)
    👌 [cve-status] Your scanner has matched the wrong artifact. The advisory is unsafe deserialization of the incremental cache of KAPT, the annotation processing plugin of the Kotlin build tooling, and the advisory database names only org.jetbrains.kotlin:kotlin-gradle-plugin. The CPE jetbrains:kotlin covers every artifact JetBrains publishes under that name, so the scanner reported it on kotlin-stdlib, which does not contain that code. The range is open because no version of kotlin-stdlib carries it. Nothing to upgrade for it.
    · cpe:2.3:a:jetbrains:kotlin::::::::
  • Vulnerabilities in: pkg:maven/org.springframework.boot/spring-boot-devtools@4.1.2 [CVE-2022-31691] (owasp)
    👌 [cve-status] Your scanner has matched the wrong product. This advisory is about Spring Tools 4 for Eclipse and the Spring Boot Tools extension for VSCode, which are editor tooling, and the dependency it was matched against is spring-boot-devtools, a different artifact that no editor ships. Nothing in a Vaadin application is affected, and nothing has to be upgraded for it.
    · cpe:2.3:a:vmware:bosh_editor::::::::
    · cpe:2.3:a:vmware:cloudfoundry_manifest_yml_support::::::::
    · cpe:2.3:a:vmware:concourse_ci_pipeline_editor::::::::
    · cpe:2.3:a:vmware:spring_boot_tools::::::::
    · cpe:2.3:a:vmware:spring_tools::::::eclipse::*
  • 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

  • 36 packages added (29 external, 7 vaadin)
  • 141 packages modified (67 external, 74 vaadin)
  • 438 packages same (286 external, 152 vaadin)

[Click for more Details]