[vaadin-bot]

No description provided.

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:maven/com.google.guava/guava@33.6.0-jre [CVE-2026-102554] (osv-bomber,osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/io.opentelemetry/opentelemetry-api@1.67.0 [CVE-2026-54285] (owasp)
    · cpe:2.3:a:opentelemetry:opentelemetry::::::node.js::*

• 🟠 Known Vulnerabilities:

  • 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/%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: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.3-SNAPSHOT since V25.3.4

  • 2 packages removed (2 external, 0 vaadin)
  • 1 packages added (1 external, 0 vaadin)
  • 144 packages modified (55 external, 89 vaadin)
  • 487 packages same (337 external, 150 vaadin)

[Click for more Details]