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-indexer. 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-indexer:4.14.10
Stacks: scratch, soc. Digest: sha256:e56f85ed9e79f113c0f2d2a7965171cd8e063262ec88e110086acdb1f69f2240.
| Severity | ID | Package | Installed | Fixed in |
|---|---|---|---|---|
| CRITICAL | CVE-2026-75595 | io.netty:netty-handler | 4.1.135.Final | 4.2.17.Final, 4.1.137.Final |
| CRITICAL | CVE-2026-8763 | org.bouncycastle:bc-fips | 2.1.2 | 1.0.2.7, 2.0.2, 2.1.3 |
| CRITICAL | CVE-2025-14813 | org.bouncycastle:bcprov-jdk15to18 | 1.79 | 1.84 |
| CRITICAL | CVE-2026-8763 | org.bouncycastle:bcprov-jdk15to18 | 1.79 | 1.85 |
| CRITICAL | CVE-2026-8763 | org.bouncycastle:bcprov-jdk15to18 | 1.84 | 1.85 |
| CRITICAL | CVE-2026-8763 | org.bouncycastle:bcprov-jdk18on | 1.84 | 1.85 |
| HIGH | CVE-2026-106451 | at.yawk.lz4:lz4-java | 1.10.1 | 1.11.4 |
| HIGH | CVE-2026-89407 | com.fasterxml.jackson.core:jackson-core | 2.18.8 | 2.18.11, 2.21.7, 2.22.3 |
| HIGH | CVE-2026-89425 | com.fasterxml.jackson.core:jackson-core | 2.18.8 | 2.21.7, 2.22.3, 2.18.11 |
| HIGH | CVE-2026-54512 | com.fasterxml.jackson.core:jackson-databind | 2.14.1 | 2.18.8, 3.1.4, 2.21.4 |
| HIGH | CVE-2026-54512 | com.fasterxml.jackson.core:jackson-databind | 2.18.2 | 2.18.8, 3.1.4, 2.21.4 |
| HIGH | CVE-2026-54513 | com.fasterxml.jackson.core:jackson-databind | 2.14.1 | 2.18.8, 2.21.4, 3.1.4 |
| HIGH | CVE-2026-54513 | com.fasterxml.jackson.core:jackson-databind | 2.18.2 | 2.18.8, 2.21.4, 3.1.4 |
| HIGH | CVE-2026-68497 | com.fasterxml.jackson.core:jackson-databind | 2.14.1 | 2.18.10, 2.21.6, 2.22.2 |
| HIGH | CVE-2026-68497 | com.fasterxml.jackson.core:jackson-databind | 2.18.2 | 2.18.10, 2.21.6, 2.22.2 |
| HIGH | CVE-2026-68497 | com.fasterxml.jackson.core:jackson-databind | 2.18.8 | 2.18.10, 2.21.6, 2.22.2 |
| HIGH | CVE-2026-91776 | com.fasterxml.jackson.core:jackson-databind | 2.14.1 | 2.18.11, 2.21.7, 2.22.3 |
| HIGH | CVE-2026-91776 | com.fasterxml.jackson.core:jackson-databind | 2.18.2 | 2.18.11, 2.21.7, 2.22.3 |
| HIGH | CVE-2026-91776 | com.fasterxml.jackson.core:jackson-databind | 2.18.8 | 2.18.11, 2.21.7, 2.22.3 |
| HIGH | CVE-2026-91777 | com.fasterxml.jackson.core:jackson-databind | 2.14.1 | 2.21.7, 2.18.11, 2.22.3 |
| HIGH | CVE-2026-91777 | com.fasterxml.jackson.core:jackson-databind | 2.18.2 | 2.21.7, 2.18.11, 2.22.3 |
| HIGH | CVE-2026-91777 | com.fasterxml.jackson.core:jackson-databind | 2.18.8 | 2.21.7, 2.18.11, 2.22.3 |
| HIGH | CVE-2026-102554 | com.google.guava:guava | 32.1.3-jre | 33.7.2 |
| HIGH | CVE-2026-102554 | com.google.guava:guava | 33.2.1-jre | 33.7.2 |
| HIGH | CVE-2026-102554 | com.google.guava:guava | 33.4.0-jre | 33.7.2 |
| 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-59901 | io.netty:netty-codec | 4.1.135.Final | 4.1.136.Final |
| HIGH | CVE-2026-55831 | io.netty:netty-codec-http | 4.1.135.Final | 4.2.16.Final, 4.1.136.Final |
| HIGH | CVE-2026-55833 | io.netty:netty-codec-http | 4.1.135.Final | 4.2.16.Final, 4.1.136.Final |
| HIGH | CVE-2026-56745 | io.netty:netty-codec-http | 4.1.135.Final | 4.2.16.Final, 4.1.136.Final |
| HIGH | CVE-2026-56819 | io.netty:netty-codec-http2 | 4.1.135.Final | 4.2.16.Final, 4.1.136.Final |
| HIGH | CVE-2026-54399 | org.apache.httpcomponents.core5:httpcore5 | 5.3.1 | 5.4.3, 5.5-beta2 |
| HIGH | CVE-2026-54428 | org.apache.httpcomponents.core5:httpcore5-h2 | 5.3.1 | 5.4.3, 5.5-beta2 |
| HIGH | CVE-2026-13505 | org.bouncycastle:bc-fips | 2.1.2 | 1.0.2.7, 2.0.2, 2.1.3 |
| HIGH | CVE-2026-13506 | org.bouncycastle:bc-fips | 2.1.2 | 1.0.2.7, 2.0.2, 2.1.3 |
| HIGH | CVE-2026-8798 | org.bouncycastle:bc-fips | 2.1.2 | 2.1.3 |
| HIGH | CVE-2026-13506 | org.bouncycastle:bcprov-jdk15to18 | 1.79 | 1.85 |
| HIGH | CVE-2026-13506 | org.bouncycastle:bcprov-jdk15to18 | 1.84 | 1.85 |
| HIGH | CVE-2026-5598 | org.bouncycastle:bcprov-jdk15to18 | 1.79 | 1.80.2 |
| HIGH | CVE-2026-13506 | org.bouncycastle:bcprov-jdk18on | 1.84 | 1.85 |
| HIGH | CVE-2026-77422 | org.jline:jline-builtins | 3.27.1 | 4.3.1, 3.30.15 |
| HIGH | CVE-2026-75140 | org.jsoup:jsoup | 1.15.3 | 1.23.2 |
| HIGH | CVE-2026-108106 | org.xerial.snappy:snappy-java | 1.1.10.7 | 1.1.10.9 |
| HIGH | CVE-2026-93451 | org.xerial.snappy:snappy-java | 1.1.10.7 | 1.1.10.9 |
| 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 |
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-indexer (6 critical, 45 high)[/-][+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 46 high)[/+]github-actions commentedon Oct 10, 2026
New since the last scan: CVE-2026-106451.
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:6a9c1e38…). I ran trivy (HIGH/CRITICAL, fixable only) againstwazuh/wazuh-indexer:4.14.9-rc2, released 2026-10-08. It clears only the Amazon Linux packages (rpm, curl, pcre2), 14 of the 42. All 28 Java findings remain, 5 of them CRITICAL: netty (handler, codec, codec-http, codec-http2), the three BouncyCastle jars, jackson-core and jackson-databind, httpcore5 and httpcore5-h2, lz4-java, jsoup and jline. Pinning the rc would buy nothing.What can be reached. The indexer is
expose-only on9200(ADR-0030's port table). Its clients are the manager's filebeat, the dashboard and Alloy, all on thesocbridge. Nothing off-host connects to it directly.When to act. When 4.14.9 ships as a stable release with all three images: scan it, bump if it is cleaner. The indexer, manager and dashboard must match to the patch version, so this is the one grouped Dependabot PR (
wazuh/*, soc and scratch together), not an indexer-only bump.CERT_TOOL_VERSIONstays4.14for a patch bump. The rc suggests the Java dependencies won't move in 4.14.9. They track the OpenSearch base under the indexer, so expect most of these to wait for a later Wazuh minor.The issue stays open and closes itself when a scan finds the pinned digest clean.
Gerrrt commentedon Oct 10, 2026
This is waiting on upstream. Nothing in the repo needs to change.
wazuh/wazuh-indexer:4.14.8(sha256:6a9c1e38…).pin-digests.shreports no drift, so the tag hasn't been rebuilt since it was pinned.com.fasterxml.jackson.core:jackson-databind: 13 findings, fixed in 5 different versions (see the table)org.bouncycastle:bcprov-jdk15to18: 6 findings, fixed in 3 different versions (see the table)org.bouncycastle:bc-fips: 4 findings, fixed in 2 different versions (see the table)io.netty:netty-codec-http: 3 findings, fixed in 4.2.16.Final, 4.1.136.Finalorg.bouncycastle:bcprov-jdk18on: 2 findings, fixed in 1.85com.fasterxml.jackson.core:jackson-core: 2 findings, fixed in 2 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 criticals, traced, 2026-10-10
This is the same trace as on #979 and #1009, applied to the deployed
wazuh-indexer:4.14.8@sha256:6a9c1e38…. The 6 critical rows are 3 CVEs. I used trivy 0.75.0's PkgPath and each advisory's precondition, then searched the bytecode of all 653 jars in the image (plugins, modules, lib, performance-analyzer-rca), excluding the flagged libraries themselves. None of the three is reachable as deployed.SniHandler/SslClientHelloHandlerchoosing per-SNISslContexts, where only some require client authSniHandler,AbstractSniHandlerorSslClientHelloHandler. The security plugin puts oneSslHandlerper listener, built fromopensearch.yml's singlessl.http.*andssl.transport.*settings. There's no per-SNI context to fall back from.root-ca.pemfrom the Wazuh 4.14 cert tool (CERT_TOOL_VERSION: "4.14"). The tool creates the root with a bareopenssl req -x509 -new … -subj '/OU=Wazuh/O=Wazuh/L=California/'and no constraints, and its leaf config hasbasicConstraints,keyUsageandsubjectAltNameonly. The 4.14wazuh-certs-tool.shcontains nonameConstraints. There is nothing to bypass.performance-analyzer-rca/lib)G3413CTRBlockCipher)cryptacularBlockCipherSpec, is a cipher-name table in a different plugin's classloader, so it can't load the RCA lib's jar. TLS is pinned to four ECDHE AES-GCM suites (plugins.security.ssl.http.enabled_ciphers).This also covers the previous triage's "BouncyCastle (TLS in the security plugin): reachable only from those three containers". Those three are filebeat, the dashboard and Alloy. The BouncyCastle critical needs a name-constrained CA, which this estate doesn't have, so it isn't reachable from them either. The HIGHs (netty HTTP/1 and HTTP/2 codecs, jackson, httpcore5) aren't covered by this trace. They stay as the triage above describes, reachable only from the
socbridge.What would change this:
None of those is on any plan.
To reproduce:
🤖 Traced by Claude Code
Gerrrt commentedon Oct 10, 2026
Rechecked 2026-10-10.
4.14.8still resolves to the pinnedsha256:6a9c1e38…, and 4.14.9 is still at rc2, so the wait above stands.Wazuh 5.0 is worse for this image, not better. I scanned
wazuh/wazuh-indexer:5.0.0-rc1with 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-rc1The 5.0 criticals are two of the same three CVEs, already traced unreachable above (no SNI routing, no name-constrained CA). The highs roughly triple: the 5.0 indexer ships older netty and jackson than 4.14.8 does, and adds netty HTTP/3. This matches the dashboard (#1009). 5.0 removes the cert-generator image (#1008) but isn't a CVE fix for the indexer or the dashboard. Don't move to it for security reasons.
Nothing in the repo changes. As noted above, the Java findings follow the OpenSearch base, so expect them to outlast 4.14.9.
Gerrrt commentedon Oct 10, 2026
Rechecked 2026-10-10. Upstream is unchanged:
4.14.8still resolves to the pinnedsha256:6a9c1e38…, 4.14.9 is at rc2 and 5.0.0 at rc1. The wait above stands.The one finding not traced yet: CVE-2026-106451, lz4-java 1.10.1 (HIGH, fixed in 1.11.4). The 14:13 scan added it. Not reachable.
plugins/opensearch-security/lz4-java-1.10.1.jar(trivy 0.75.0 PkgPath).net.jpountz.util.Native.load()creates an exclusive.lcktemp file, then writes the native library to the predictable path next to it without exclusive creation. Another local user who can write to the same temp directory can win the race and swap the.sobeforeSystem.load(), giving code execution as the JVM's user.config/jvm.optionssets-Djava.io.tmpdir=${OPENSEARCH_TMPDIR}.bin/opensearchfills that from OpenSearch'sTempDirectorylauncher, which callsFiles.createTempDirectory("opensearch-"), a fresh directory with mode 0700 owned by the JVM's user. Only that user,wazuh-indexer(uid 1000), can write there. It's the container's only login user, and nothing else runs in the container. An attacker able to write to that directory already runs as the indexer, so they gain nothing.This doesn't change what closes the issue: these Java rows follow upstream's OpenSearch base, as noted above.
Gerrrt commentedon Oct 10, 2026
The HIGHs, traced, 2026-10-10
This follows the criticals trace above, using the same image (
wazuh-indexer:4.14.8@sha256:6a9c1e38…) and the same method. There are 23 distinct Java (CVE, package) HIGHs; the Amazon Linux rpm, curl and pcre2 rows aren't on the JVM's path. For each one I took the advisory's trigger and searched the bytecode of every jar in the image (excluding the flagged libraries themselves) inside a throwaway--network nonecontainer, usingjavapfrom the bundled JDK where call sites mattered. None is reachable from thesocbridge.What listens. The only listener is REST on 9200 (transport-netty4 HTTP/1.1, TLS from the security plugin), plus 9300 transport for this single node. The image ships Performance Analyzer's agent configured for an unauthenticated webservice on 9600 and gRPC on 9650, but nothing starts it. Only
supervisord.confreferencesperformance-analyzer-agent, the image has nosupervisordbinary, and/entrypoint.shjust execsbin/opensearch. (That's from the image; I didn't runsson odin.)io/netty/handler/codec/spdy/.Bzip2Decoder.DelegatingDecompressorFrameListener)httpclient5(client). There's noServerBootstraporH2ServerBootstrap. It's reachable only through an ML remote connector to a hostile endpoint. Nothing in this repo creates one; I didn't query odin's indexer to confirm none exists.PolymorphicTypeValidatoractivateDefaultTyping,enableDefaultTypingor PTV use in any plugin.@JsonTypeInfowithdefaultImpl/@JsonIdentityInfojavax.xml.datatype.Duration/XMLGregorianCalendarlooksLikeValidNumber(databind coercion) /createParser(DataInput)Security.addProvider, i.e. last, so JSSE parses and validates certificates with the JDK provider. BC ASN.1 runs only inparseOtherName/getOtherNamefor SAN extraction, on certificates that have already chained to our root (clientauthcan't skip validation), and in the admin_plugins/_security/api/ssl/certsAPI on our own certs.xmlParser/XmlTreeBuilderuse.grepbuiltinThis firms up the earlier triage's "netty HTTP/1 and HTTP/2, BouncyCastle: reachable only from those three containers". With the bug-specific code paths checked, they aren't reachable from those three either.
What would change this:
To reproduce:
🤖 Traced by Claude Code
Gerrrt commentedon Oct 10, 2026
The Amazon Linux rows, 2026-10-10
The HIGHs trace above set these aside as "not on the JVM's path". That's true, but something in the container does run curl and grep, so here they are against the pinned
wazuh-indexer:4.14.8@sha256:6a9c1e38…. There are 14 rows covering 4 CVEs. None is reachable.curl-minimal,libcurl-minimal--pinnedpubkey/CURLOPT_PINNEDPUBLICKEY) set together with verification turned off. The pin then isn't enforced when the server presents no certificate.curl -fsk --cert … https://localhost:9200/_cluster/healthevery 30 s. It turns verification off (-k) but pins nothing. Neitherstacks/socnorstacks/scratchuses--pinnedpubkey.pcre2,pcre2-syntaxpcre2_jit_matchwith a previously copied subject passed in as context, on input an attacker controls./entrypoint.shrunsgrep -oP(PCRE) twice at boot, but only over our ownconfig/opensearch.yml. The healthcheck'sgrep -q '"status"'is a basic regex, not PCRE. The JVM doesn't use pcre2.rpm,rpm-libs,rpm-build-libs,rpm-sign-libs,python3-rpmrpmbuildprocessing a crafted tarball, orrpmuncompress -xon a crafted.gemfilename/usr/bin/rpmbuildandrpmuncompressare absent), and nothing runsrpmafter the buildWhat would change this: adding
--pinnedpubkeyto the healthcheck while keeping-k; an entrypoint that runsgrep -Pover input we don't write; or a derived image that installsrpm-build.This completes the trace for all 52 rows. The issue still waits on 4.14.9, and the OS rows should clear with it: 4.14.9-rc2 already drops the same Amazon Linux findings from the manager image (#1011).
To reproduce:
🤖 Traced by Claude Code
[-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 46 high)[/-][+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 69 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-indexer (6 critical, 69 high)[/-][+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 84 high)[/+]github-actions commentedon Oct 26, 2026
New since the last scan: CVE-2026-103111, CVE-2026-19553, CVE-2026-78659, CVE-2026-78667, CVE-2026-86145, CVE-2026-89156, CVE-2026-89160, CVE-2026-92392, CVE-2026-94440.
[-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 84 high)[/-][+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 87 high)[/+]github-actions commentedon Nov 2, 2026
New since the last scan: CVE-2026-102554, CVE-2026-108106, CVE-2026-93451.
[-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 87 high)[/-][+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 37 high)[/+][-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 37 high)[/-][+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 71 high)[/+]github-actions commentedon Nov 16, 2026
New since the last scan: CVE-2026-103242, 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.