[ZheSun88]

No description provided.

[github-actions]

Dependencies Report

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:maven/io.opentelemetry/[email protected] [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/[email protected] [CVE-2026-118246, CVE-2026-118251, CVE-2026-118244, CVE-2026-116796, CVE-2026-118250] (osv-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: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/[email protected] [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/[email protected] [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:javascript/[email protected] [CVE-2025-15056, CVE-2026-120350] (owasp)
    👌 [cve-status] Fixed on this line from 25.4.0-alpha5. That prerelease pins @vaadin/rich-text-editor 25.4.0-alpha5, whose vendored Quill escapes the video and formula values before building the semantic HTML, and the reproduction that fires on 25.4.0-alpha4, through the control and through RichTextEditor.asDelta(), does not fire here. The patched copy keeps Quill's own version string 2.0.3, because the fix is ours and there is no Quill release to move to, so a scanner reading the bundled file reports the advisory on this version anyway. That report is stale, not a second finding. CVE-2026-120350 names this same flaw: it is the advisory Vaadin itself published for it, and CVE-2025-15056 is the id under which it was first reported, so a scanner may lead with either. One record, one fix, and this verdict answers both ids.
    · cpe:2.3:a:slab:quill:2.0.3:::::node.js::
  • Vulnerabilities in: pkg:maven/com.vaadin/[email protected] [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-alpha6

  • 17 packages modified (17 external, 0 vaadin)
  • 604 packages same (371 external, 233 vaadin)

[Click for more Details]