Repository navigation
Open
Labels
scratchstacks/scratch on diabolos (VLAN 30)stacks/scratch on diabolos (VLAN 30)securityA credential, an exposure, or a control that is weaker than recordedA credential, an exposure, or a control that is weaker than recordedsocstacks/soc on odin (VLAN 30)stacks/soc on odin (VLAN 30)
Description
The weekly CVE scan found fixable HIGH or CRITICAL vulnerabilities in wazuh/wazuh-dashboard. This body is rewritten by every scan, and the issue closes itself when a scan finds the pinned digest clean.
The fix is normally the Dependabot bump for this image. If upstream has not released one, the fixed versions below say what to wait for.
wazuh/wazuh-dashboard:4.14.10
Stacks: scratch, soc. Digest: sha256:0eebab19802342b841a258f56d6fa0fb085cdae08ab5eb2e45f9455c906d719a.
| Severity | ID | Package | Installed | Fixed in |
|---|---|---|---|---|
| CRITICAL | GHSA-cg2g-xh64-v4q7 | dompurify | 3.4.11 | 3.4.17 |
| CRITICAL | CVE-2026-106445 | handlebars | 4.7.9 | 4.7.10 |
| CRITICAL | CVE-2026-106446 | handlebars | 4.7.9 | 4.7.10 |
| CRITICAL | CVE-2026-85061 | maplibre-gl | 2.4.0 | 6.4.1 |
| CRITICAL | CVE-2026-90711 | proxy-addr | 2.0.7 | 2.0.8 |
| CRITICAL | CVE-2026-59873 | tar | 7.5.16 | 7.5.19 |
| HIGH | CVE-2026-119202 | @hapi/content | 6.0.2 | 6.0.3 |
| HIGH | CVE-2026-104850 | @modelcontextprotocol/sdk | 1.27.1 | 1.31.0 |
| HIGH | CVE-2026-111767 | @modelcontextprotocol/sdk | 1.27.1 | 1.32.0 |
| HIGH | CVE-2026-111768 | @modelcontextprotocol/sdk | 1.27.1 | 1.32.0 |
| HIGH | GHSA-f897-62hf-6gxq | @modelcontextprotocol/sdk | 1.27.1 | 1.30.1 |
| HIGH | CVE-2026-101898 | axios | 1.18.1 | 1.20.0 |
| HIGH | CVE-2026-101901 | axios | 1.18.1 | 1.20.0 |
| HIGH | CVE-2026-101903 | axios | 1.18.1 | 1.20.0 |
| HIGH | CVE-2026-101905 | axios | 1.18.1 | 1.20.0 |
| HIGH | CVE-2026-101906 | axios | 1.18.1 | 1.20.0 |
| HIGH | CVE-2026-101907 | axios | 1.18.1 | 1.20.0 |
| HIGH | CVE-2026-101909 | axios | 1.18.1 | 0.34.0, 1.20.0 |
| HIGH | CVE-2026-102990 | basic-ftp | 5.3.1 | 6.2.1 |
| HIGH | CVE-2026-111181 | body-parser | 2.2.2 | 2.4.0, 1.20.9 |
| HIGH | CVE-2026-102276 | brace-expansion | 1.1.15 | 5.0.10, 3.0.7, 2.1.5, 1.1.19 |
| HIGH | CVE-2026-102276 | brace-expansion | 2.1.1 | 5.0.10, 3.0.7, 2.1.5, 1.1.19 |
| HIGH | CVE-2026-102278 | brace-expansion | 1.1.15 | 5.0.11, 3.0.8, 2.1.6, 1.1.20 |
| HIGH | CVE-2026-102278 | brace-expansion | 2.1.1 | 5.0.11, 3.0.8, 2.1.6, 1.1.20 |
| HIGH | CVE-2026-13149 | brace-expansion | 1.1.15 | 5.0.7, 1.1.16, 2.1.2 |
| HIGH | CVE-2026-13149 | brace-expansion | 2.1.1 | 5.0.7, 1.1.16, 2.1.2 |
| HIGH | CVE-2026-14257 | brace-expansion | 1.1.15 | 5.0.8, 3.0.3, 2.1.3, 1.1.17 |
| HIGH | CVE-2026-14257 | brace-expansion | 2.1.1 | 5.0.8, 3.0.3, 2.1.3, 1.1.17 |
| HIGH | CVE-2026-69152 | brace-expansion | 1.1.15 | 1.1.18, 2.1.4, 3.0.6, 5.0.9 |
| HIGH | CVE-2026-69152 | brace-expansion | 2.1.1 | 1.1.18, 2.1.4, 3.0.6, 5.0.9 |
| HIGH | CVE-2026-118664 | decode-uri-component | 0.2.2 | 0.5.1 |
| HIGH | GHSA-mrv2-3pqr-j5jr | dompurify | 3.4.11 | 3.4.17 |
| HIGH | CVE-2026-13676 | fast-uri | 3.1.0 | 4.0.1, 3.1.3, 2.4.2 |
| HIGH | CVE-2026-16221 | fast-uri | 3.1.0 | 2.4.3, 3.1.4, 4.1.1 |
| HIGH | CVE-2026-18446 | fast-uri | 3.1.0 | 2.4.4, 3.1.5, 4.1.2 |
| HIGH | CVE-2026-6321 | fast-uri | 3.1.0 | 3.1.1, 2.4.1 |
| HIGH | CVE-2026-6322 | fast-uri | 3.1.0 | 3.1.2, 2.4.1 |
| HIGH | CVE-2026-75975 | fast-uri | 3.1.0 | 2.4.5, 3.1.6, 4.1.3 |
| HIGH | CVE-2026-76172 | fast-uri | 3.1.0 | 2.4.5, 3.1.6, 4.1.3 |
| HIGH | CVE-2026-84292 | fast-uri | 3.1.0 | 2.4.6, 3.1.7, 4.1.4 |
| HIGH | CVE-2026-111755 | follow-redirects | 1.16.0 | 1.16.1 |
| HIGH | CVE-2026-111756 | follow-redirects | 1.16.0 | 1.16.1 |
| HIGH | CVE-2026-116689 | follow-redirects | 1.16.0 | 1.16.2 |
| HIGH | CVE-2026-12143 | form-data | 4.0.5 | 2.5.6, 3.0.5, 4.0.6 |
| HIGH | CVE-2026-86805 | glibc | 2.34-231.amzn2023.0.5 | 2.34-231.amzn2023.0.6 |
| HIGH | CVE-2026-86805 | glibc-common | 2.34-231.amzn2023.0.5 | 2.34-231.amzn2023.0.6 |
| HIGH | CVE-2026-86805 | glibc-minimal-langpack | 2.34-231.amzn2023.0.5 | 2.34-231.amzn2023.0.6 |
| HIGH | CVE-2026-69192 | ip-address | 10.2.0 | 10.3.1 |
| HIGH | CVE-2026-69192 | ip-address | 6.4.0 | 10.3.1 |
| HIGH | CVE-2026-46625 | js-cookie | 2.2.1 | 3.0.7 |
| HIGH | CVE-2026-59869 | js-yaml | 4.1.1 | 3.15.0, 4.3.0 |
| HIGH | CVE-2026-84375 | js-yaml | 4.1.1 | 4.3.2, 3.15.2 |
| HIGH | GHSA-5p4m-2wfm-xmqj | js-yaml | 4.1.1 | 4.3.1, 3.15.1 |
| HIGH | CVE-2026-118779 | node-forge | 1.4.0 | 1.4.1 |
| HIGH | CVE-2026-118782 | node-forge | 1.4.0 | 1.4.1 |
| HIGH | CVE-2026-119187 | node-forge | 1.4.0 | 1.4.1 |
| HIGH | CVE-2026-119188 | node-forge | 1.4.0 | 1.4.1 |
| HIGH | CVE-2026-119190 | node-forge | 1.4.0 | 1.4.1 |
| HIGH | CVE-2026-119191 | node-forge | 1.4.0 | 1.4.1 |
| HIGH | CVE-2026-119192 | node-forge | 1.4.0 | 1.4.1 |
| HIGH | CVE-2026-103242 | python3-rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-84837 | python3-rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95519 | python3-rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95520 | python3-rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-95521 | python3-rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-103242 | rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-84837 | rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95519 | rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95520 | rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-95521 | rpm | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-103242 | rpm-build-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-84837 | rpm-build-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95519 | rpm-build-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95520 | rpm-build-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-95521 | rpm-build-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-103242 | rpm-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-84837 | rpm-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95519 | rpm-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95520 | rpm-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-95521 | rpm-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-103242 | rpm-sign-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-84837 | rpm-sign-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95519 | rpm-sign-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.9 |
| HIGH | CVE-2026-95520 | rpm-sign-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-95521 | rpm-sign-libs | 4.16.1.3-29.amzn2023.0.8 | 4.16.1.3-29.amzn2023.0.10 |
| HIGH | CVE-2026-119371 | sqlite-libs | 3.40.0-1.amzn2023.0.8 | 3.40.0-1.amzn2023.0.9 |
| HIGH | CVE-2026-119372 | sqlite-libs | 3.40.0-1.amzn2023.0.8 | 3.40.0-1.amzn2023.0.9 |
| HIGH | CVE-2026-119373 | sqlite-libs | 3.40.0-1.amzn2023.0.8 | 3.40.0-1.amzn2023.0.9 |
| HIGH | CVE-2026-119375 | sqlite-libs | 3.40.0-1.amzn2023.0.8 | 3.40.0-1.amzn2023.0.9 |
| HIGH | CVE-2026-119376 | sqlite-libs | 3.40.0-1.amzn2023.0.8 | 3.40.0-1.amzn2023.0.9 |
| HIGH | CVE-2026-119378 | sqlite-libs | 3.40.0-1.amzn2023.0.8 | 3.40.0-1.amzn2023.0.9 |
| HIGH | CVE-2026-59874 | tar | 7.5.16 | 7.5.18 |
| HIGH | CVE-2026-73566 | tar | 7.5.16 | 7.5.21 |
Written by .github/workflows/cve-scan.yml in this run.
Metadata
Metadata
Assignees
Labels
scratchstacks/scratch on diabolos (VLAN 30)stacks/scratch on diabolos (VLAN 30)securityA credential, an exposure, or a control that is weaker than recordedA credential, an exposure, or a control that is weaker than recordedsocstacks/soc on odin (VLAN 30)stacks/soc on odin (VLAN 30)
Activity
[-]Fixable CVEs in wazuh/wazuh-dashboard (4 critical, 52 high)[/-][+]Fixable CVEs in wazuh/wazuh-dashboard (6 critical, 52 high)[/+]github-actions commentedon Oct 10, 2026
New since the last scan: CVE-2026-106445, CVE-2026-106446.
Gerrrt commentedon Oct 10, 2026
Triage (2026-10-10): waiting on upstream. No change to the pin.
There is no fixed image yet.
4.14.8is the latest stable Wazuh release, and the tag still resolves to the digest we pin (sha256:dd338d22…). I ran trivy (HIGH/CRITICAL, fixable only) againstwazuh/wazuh-dashboard:4.14.9-rc2, released 2026-10-08. It clears 16 of the 51: the Amazon Linux packages (rpm, curl, pcre2),ws, and one of the twoform-datacopies. The other 35 npm findings remain, 5 of them CRITICAL (handlebars×2,form-data3.0.1,maplibre-gl,proxy-addr,tar). Pinning the rc would buy nothing.What can be reached. This is the one Wazuh image with an HTTP listener on the network:
5601is published as${BIND_ADDR}:443, directly, with no proxy in front. It is reachable from VLAN 30 and from Hicks over the 50 -> 30 rule. Not from the internet.proxy-addr,fast-uri,js-yaml,handlebars: server-side code in OpenSearch Dashboards, and the plausible path for request input. Reachable from anything on VLAN 30 and from Hicks, before login for whatever the login and status routes touch, the rest only after login.axios,form-data: outbound, the dashboard's own calls to the indexer and the manager API on thesocbridge. An attacker would need to control one of those responses.maplibre-gl,js-cookie: browser-side. They run in the viewer's browser, not the container.tar,basic-ftp,brace-expansion,ip-address,@modelcontextprotocol/sdk: bundled with the build or the plugin tooling. Not on the request path as configured.When to act. When 4.14.9 ships as a stable release with all three images: scan it, bump if it is cleaner. The dashboard has to match the indexer and manager to the patch version, so it is the one grouped Dependabot PR (
wazuh/*, soc and scratch together).CERT_TOOL_VERSIONstays4.14. If the dashboard needs narrowing before then,BIND_ADDRalready limits it to odin's address. A firewall rule allowing only Hicks to reach443would cut the VLAN 30 exposure.The issue stays open and closes itself when a scan finds the pinned digest clean.
Gerrrt commentedon Oct 10, 2026
Opened #1139 for the exposure noted above. It turns out a pfSense rule can't narrow the dashboard: VLAN 30 traffic to odin never passes through pfSense, so every lab host can reach
:443, not just Hicks. #1139 proposes the:8448pattern instead: the SOC Caddy in front of the dashboard, answering only10.0.50.0/24. This issue still waits on 4.14.9 as before.Gerrrt commentedon Oct 10, 2026
This is waiting on upstream. Nothing in the repo needs to change.
wazuh/wazuh-dashboard:4.14.8(sha256:dd338d22…).pin-digests.shreports no drift, so the tag hasn't been rebuilt since it was pinned.brace-expansion: 10 findings, fixed in 5 different versions (see the table)fast-uri: 8 findings, fixed in 7 different versions (see the table)axios: 7 findings, fixed in 2 different versions (see the table)form-data: 3 findings, fixed in 2 different versions (see the table)tar: 3 findings, fixed in 3 different versions (see the table)js-yaml: 3 findings, fixed in 3 different versions (see the table)When upstream rebuilds or ships a release with these fixes, Dependabot should open the bump. Check it with trivy and
check_image_pins.py, then deploy. The next scan will then close this issue.Gerrrt commentedon Oct 10, 2026
The six criticals, traced, 2026-10-10
This is the same trace as on #979, applied to the deployed
wazuh-dashboard:4.14.8@sha256:dd338d22…. I used trivy 0.75.0's PkgPath and each advisory's precondition, then read the image's server code and everypackage.jsonunder/usr/share/wazuh-dashboard, counting runtimedependenciesonly, not dev. None of the six is reachable server-side from the network. One, maplibre-gl, is a browser-side XSS that needs a hostile map attribution.node_modules/)allowProtoMethodsByDefaultsrc/legacy/ui/ui_render/bootstrap/app_bootstrap.js, which compiles the fixed on-disktemplate.js.hbswith{ knownHelpersOnly, noEscape, strict }and no prototype-access option.compile()fs.readFile.node_modules/)trust proxyentry@modelcontextprotocol/sdkandexpress-rate-limitonly, and no server code requires either. The only matches are browser bundles underplugins/*/target/public. Nothing callsproxy-addr.node_modules/)tar←cacache←compression-webpack-plugin, which is build tooling. Nothing insrc/orplugins/requires it.plugins/wazuh/node_modules/)jsdom. The plugin uses jsdom only as an emptynew JSDOM('').windowfor DOMPurify inserver/lib/sanitizer/sanitizer.js, which sanitizes uploaded SVG logos. form-data is used by jsdom's XHR, and the sanitizer never makes a request.plugins/customImportMapDashboards/)map.*inopensearch_dashboards.yml). Custom attribution is set through the layer config UI, and the dashboard's only human login isadmin(internal_users.yml). The other source is the style manifest from OpenSearch's maps service, which the browser fetches when a map is opened.adminalone, or a compromised OpenSearch maps service. Nothing from VLAN 30 without logging in.What this means for #1139: the server-side criticals don't make the published
:443worse than a login page with a Node.js backend. The 4.14.9 wait and #1139's narrowing still stand as written. The case for #1139 rests on the login surface itself and on the HIGHs, which this trace doesn't cover. The triage above namesfast-uriandjs-yamlas plausible request-path code. It doesn't rest on these six.What would change this:
admin.requireexpress, the MCP SDK, ortar.To reproduce:
🤖 Traced by Claude Code
Gerrrt commentedon Oct 10, 2026
Rechecked 2026-10-10, with two updates.
1. The exposure fix has merged, but isn't confirmed on odin yet. #1152 (merged 16:02 UTC) moves the dashboard behind the SOC Caddy, answering only
10.0.50.0/24. That narrows the:443login surface the triage above was concerned with, from all of VLAN 30 to Hicks. #1139 stays open until the post-merge checks on odin pass. Until then, assume the old exposure.2. Wazuh 5.0 is not a way out for this image. I scanned
wazuh/wazuh-dashboard:5.0.0-rc1(pushed 2026-10-05) with trivy 0.75.0 andscan-images.sh's flags (--image-src remote --platform linux/amd64 --scanners vuln --severity HIGH,CRITICAL --ignore-unfixed):4.14.8(pinned)5.0.0-rc1It drops
form-dataandproxy-addr(both traced unreachable above) but carries more highs. So 5.0 would clear #1008 by removing the cert-generator image, but it would not clean up the dashboard. The 4.14.9 stable release is still the bump to wait for. The rc2 scan above already showed it leaves the criticals in place, so expect this issue to outlast that bump too.Nothing in the repo changes for this issue.
Gerrrt commentedon Oct 10, 2026
The HIGHs, traced, 2026-10-10
This follows the criticals trace above, using the same image (
wazuh-dashboard:4.14.8@sha256:dd338d22…) and the same method. For every flagged npm package I built its chain of runtime dependents (dependencies/optional/peer, not dev) up to OSD core or a plugin, then found the actualrequiresites in server code (src/,plugins/*/server) and what feeds them. I excludedtarget/publicand anything underpublic/, which is browser code. There are 45 distinct (CVE, package) HIGHs. None is reachable from an inbound request without a dashboard administrator login, and the one that needs that login isn't reachable either.ajv← the MCP SDK (never loaded) · ←fast-json-stringify←@elastic/ecs-pino-format←elastic-apm-node· ←schema-utils(webpack)ajvorfast-uridirectly. The APM agent compiles its own fixed schemas.!!omap)@osd/config,@osd/apm-config-loadertelemetry.ymlloading: files on disk. (2) wazuhCoreconfiguration-store.jsreadConfigurationFile():load()swazuh.yml. That file is rewritten byPUT /utils/configuration, which needsrouteDecoratorProtectedAdministratorandConfigurationAPIEditable. Values are written asJSON.stringifyfor objects, which can't express anchors, aliases or!!omap, and as"…"for strings with newlines escaped, so each value stays on one line. None of the three DoS shapes (alias-chained merges, aliased empty mappings,!!omap) can be written that way.@osd/ui-shared-deps(browser)rendering_service.js:axios.get(brandingUrl, {maxRedirects: 0}), with the URL fromopensearchDashboards.branding.*, which we don't set. (2) wazuhCoreserver-api-client.js:axios.create({httpsAgent})to${api.url}:${api.port}${path}(the manager API). The triggers are HTTP/2 (httpVersion: 2, unused), proxy env (none: no*_proxyin the image or our compose), the fetch adapter (Node uses the http adapter), an attacker-supplieddata:URL (the base is fixedhttps://), and two that need a separate prototype-pollution bug to chain from.minimatch←glob← cacache/rimraf/del (tooling) · ←archiver/unzipper←exceljs(Reports)wildcard_matcher.js:new Minimatch(pattern)with patterns from console proxy config. Brace expansion runs on the pattern, never on the matched request path. (2) ReportsexcelBuilder.js→ exceljs → archiver, which writes buffers and globs only fixed internal patterns.cacache←compression-webpack-pluginjsdom(Wazuh, Reports)new JSDOM('').windowfor DOMPurify (traced above). No page script opens a WebSocket.axios(browser) ·jsdomsocks/get-uri←proxy-agent← securityDashboardsauth/types/openid/openid_auth.js. We run internal-user basic auth: noopenid,samlor proxy settings inopensearch_dashboards.yml.react-use(browser)curl -sk … /app/login, with no--pinnedpubkey. The bug needs pinning plus verification off.nodedoesn't link pcre2 (V8 has its own regex engine).rpmuncompress, which nothing runs.For #1139: with the criticals and the HIGHs both traced, nothing in this image's server-side request handling is reachable from VLAN 30 through a vulnerable library. #1139's case is the login page itself on
:443, unchanged by the CVE list, plus the browser-side maplibre item above.Aside, not a CVE: wazuhCore's string formatter escapes only the first
"(value.replace(/"/, '\\"'), nogflag). An administrator saving a setting value with two or more"could write a malformedwazuh.ymlline. That needs the dashboard administrator, and newlines are escaped, so it can't inject the multi-line YAML the js-yaml DoS needs. It may be worth reporting upstream.What would change this:
*_proxyenv on the dashboard.opensearch_dashboards.yml.To reproduce:
🤖 Traced by Claude Code
[-]Fixable CVEs in wazuh/wazuh-dashboard (6 critical, 52 high)[/-][+]Fixable CVEs in wazuh/wazuh-dashboard (6 critical, 75 high)[/+]github-actions commentedon Oct 19, 2026
New since the last scan: CVE-2026-35189, CVE-2026-35191, CVE-2026-42772, CVE-2026-54872, CVE-2026-54873, CVE-2026-72897, CVE-2026-75804, CVE-2026-75805, CVE-2026-75806, CVE-2026-84782, CVE-2026-84784, CVE-2026-97689.
[-]Fixable CVEs in wazuh/wazuh-dashboard (6 critical, 75 high)[/-][+]Fixable CVEs in wazuh/wazuh-dashboard (7 critical, 97 high)[/+]github-actions commentedon Oct 26, 2026
New since the last scan: CVE-2023-54404, CVE-2026-103111, CVE-2026-111181, CVE-2026-111755, CVE-2026-111756, CVE-2026-111767, CVE-2026-111768, CVE-2026-19553, CVE-2026-78659, CVE-2026-78667, CVE-2026-86145, CVE-2026-89156, CVE-2026-89160, CVE-2026-92392, CVE-2026-94440, GHSA-cg2g-xh64-v4q7, GHSA-mrv2-3pqr-j5jr.
[-]Fixable CVEs in wazuh/wazuh-dashboard (7 critical, 97 high)[/-][+]Fixable CVEs in wazuh/wazuh-dashboard (7 critical, 103 high)[/+]github-actions commentedon Nov 2, 2026
New since the last scan: CVE-2026-116689, CVE-2026-118664, CVE-2026-118779, CVE-2026-118782, CVE-2026-119187, CVE-2026-119188, CVE-2026-119190, CVE-2026-119202, GHSA-f897-62hf-6gxq.
[-]Fixable CVEs in wazuh/wazuh-dashboard (7 critical, 103 high)[/-][+]Fixable CVEs in wazuh/wazuh-dashboard (6 critical, 51 high)[/+][-]Fixable CVEs in wazuh/wazuh-dashboard (6 critical, 51 high)[/-][+]Fixable CVEs in wazuh/wazuh-dashboard (6 critical, 87 high)[/+]github-actions commentedon Nov 16, 2026
New since the last scan: CVE-2026-103242, CVE-2026-119191, CVE-2026-119192, CVE-2026-119371, CVE-2026-119372, CVE-2026-119373, CVE-2026-119375, CVE-2026-119376, CVE-2026-119378, CVE-2026-84837, CVE-2026-86805, CVE-2026-95519, CVE-2026-95520, CVE-2026-95521.