Update flow to 25.2.11

[vaadin-bot]

No description provided.

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:maven/tools.jackson.core/jackson-core@3.1.5 [CVE-2026-89425, CVE-2026-89407] (osv-bomber,osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/tools.jackson.core/jackson-databind@3.1.5 [CVE-2026-91777, CVE-2026-83557, CVE-2026-68497, CVE-2026-19032, CVE-2026-91776] (osv-bomber,osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/com.fasterxml.jackson.core/jackson-core@2.22.1 [CVE-2026-89425, CVE-2026-89407] (osv-bomber,osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.22.1 [CVE-2026-91777, CVE-2026-83557, CVE-2026-68497, CVE-2026-19032, CVE-2026-91776] (osv-bomber,osv-scan)
    👌 Not affected: Vaadin and Hilla deserialize endpoint input with the default Jackson mapper. The bypass requires MapperFeature.ACCEPT_CASE_INSENSITIVE_PROPERTIES, which Vaadin does not enable (verified in Hilla JacksonObjectMapperFactory). vulnerable_code_not_in_execute_path. Tracked upstream in Update vulnerable transitive dependencies: Jackson 2, Jackson 3 and Kotlin hilla#5801 and Update jackson-databind to 2.22.1 appsec-kit#238.
    ·
  • Vulnerabilities in: pkg:maven/tools.jackson.core/jackson-core@2.22.1 [CVE-2026-89425, CVE-2026-89407] (osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/tools.jackson.core/jackson-databind@2.22.1 [CVE-2026-91777, CVE-2026-83557, CVE-2026-68497, CVE-2026-19032, CVE-2026-91776] (osv-scan)
    👌 False report: the resolved tools.jackson jackson-databind (3.1.5) is not affected per osv.dev. This entry is a SBOM version mislabel. Tracked upstream in Update vulnerable transitive dependencies: Jackson 3 and Kotlin flow#24962 and Update vulnerable transitive dependencies: Jackson 2, Jackson 3 and Kotlin hilla#5801.
    ·
  • Vulnerabilities in: pkg:maven/com.fasterxml.jackson.core/jackson-core@3.1.5 [CVE-2026-89425, CVE-2026-89407] (osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/com.fasterxml.jackson.core/jackson-databind@3.1.5 [CVE-2026-91777, CVE-2026-83557, CVE-2026-68497, CVE-2026-19032, CVE-2026-91776] (osv-scan)
    ·

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:npm/%40apidevtools/json-schema-ref-parser@11.7.2 [CVE-2026-15195] (oss-bomber)
    👌 The cve carries a git only range with no version mapping. The affected releases are 15.3.0 to 15.3.5, fixed in 15.3.6, while 11.7.2 predates that line by 17 months. It arrives through swagger-parser 10.1.1, which pins it exactly.
    ·
  • 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.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/io.opentelemetry/opentelemetry-api@1.65.0 [CVE-2026-54285] (owasp)
    👌 False positive: the advisory is for opentelemetry-js and the CPE that matched targets node.js (cpe:2.3:a:opentelemetry:opentelemetry::::::node.js::), not the Java artifact. It reaches the sbom transitively through selenium-remote-driver under vaadin-testbench, a test only dependency. Same case as the 1.64.0 entry below.
    · cpe:2.3:a:opentelemetry:opentelemetry::::::node.js::
  • 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.9

  • 96 packages modified (11 external, 85 vaadin)
  • 560 packages same (407 external, 153 vaadin)

[Click for more Details]