chore: update versions.json in 25.2 with latest WC

[vaadin-bot]

No description provided.

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:maven/io.opentelemetry/opentelemetry-api@1.62.0 [CVE-2026-54285] (owasp)
    · cpe:2.3:a:opentelemetry:opentelemetry::::::node.js::*
  • Vulnerabilities in: pkg:maven/io.opentelemetry/opentelemetry-common@1.64.0 [CVE-2026-54285] (owasp)
    · cpe:2.3:a:opentelemetry:opentelemetry::::::node.js::*
  • Vulnerabilities in: pkg:maven/org.springframework.security/spring-security-core@7.1.0 [CVE-2026-59270, CVE-2026-47841, CVE-2026-47842, CVE-2026-47877, CVE-2026-59276, CVE-2026-59277] (owasp)
    · cpe:2.3:a:vmware:spring_security::::::::
  • Vulnerabilities in: pkg:maven/org.springframework.security/spring-security-oauth2-core@7.0.6 [CVE-2026-59270, CVE-2026-47841, CVE-2026-47842, CVE-2026-47877, CVE-2026-59276] (owasp)
    · cpe:2.3:a:vmware:spring_security::::::::
  • Vulnerabilities in: pkg:maven/org.springframework.security/spring-security-web@7.0.6 [CVE-2026-59270, CVE-2026-47841, CVE-2026-47842, CVE-2026-47877, CVE-2026-59276] (owasp)
    · cpe:2.3:a:vmware:spring_security::::::::

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:npm/%40opentelemetry/core@1.9.0 [CVE-2026-54285] (osv-bomber,osv-scan)
    👌 Not affected: @opentelemetry/core is a transitive dep of the browser Web SDK and is used only to ORIGINATE spans. The vulnerable W3CBaggagePropagator.extract() (inbound untrusted baggage parsing) is never on the execution path. vulnerable_code_not_in_execute_path.
    ·
  • Vulnerabilities in: pkg:npm/%40opentelemetry/core@1.8.0 [CVE-2026-54285] (osv-scan)
    👌 Not affected: @opentelemetry/core is a transitive dep of the browser Web SDK and is used only to ORIGINATE spans. The vulnerable W3CBaggagePropagator.extract() (inbound untrusted baggage parsing) is never on the execution path. 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-reflect@2.1.21 [CVE-2026-53914] (owasp)
    👌 False positive: the report only affects org.jetbrains.kotlin:kotlin-gradle-plugin, and the CPE for the kotlin product matches any kotlin artifact. We ship kotlin-reflect as a transitive dependency of hilla-typescript-generator, not the gradle plugin. osv.dev reports kotlin-reflect 2.1.21 as not affected.
    · cpe:2.3:a:jetbrains:kotlin::::::::
  • Vulnerabilities in: pkg:maven/org.jetbrains.kotlin/kotlin-stdlib@2.4.0 [CVE-2026-53914] (owasp)
    👌 False positive: osv.dev reports kotlin-stdlib 2.4.0 as not affected. owasp flags it via imprecise CPE matching. kotlin-stdlib comes from flow-webpush, which already declares 2.4.0.
    · cpe:2.3:a:jetbrains:kotlin::::::::
  • 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.2-SNAPSHOT since V25.2.7

  • 104 packages modified (24 external, 80 vaadin)
  • 554 packages same (396 external, 158 vaadin)

[Click for more Details]