Skip to content

Fixable CVEs in wazuh/wazuh-indexer (6 critical, 71 high) #1010

Open

Description

@github-actions

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.

Activity

  1. added
    securityA credential, an exposure, or a control that is weaker than recorded
    socstacks/soc on odin (VLAN 30)
    scratchstacks/scratch on diabolos (VLAN 30)
    on Oct 7, 2026
  2. changed the title [-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 45 high)[/-] [+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 46 high)[/+] on Oct 10, 2026
  3. github-actions commented on Oct 10, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-106451.

  4. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Triage (2026-10-10): waiting on upstream. No change to the pin.

    There is no fixed image yet. 4.14.8 is the latest stable Wazuh release, and the tag still resolves to the digest we pin (sha256:6a9c1e38…). I ran trivy (HIGH/CRITICAL, fixable only) against wazuh/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 on 9200 (ADR-0030's port table). Its clients are the manager's filebeat, the dashboard and Alloy, all on the soc bridge. Nothing off-host connects to it directly.

    • netty HTTP/1 and HTTP/2, BouncyCastle (TLS in the security plugin): reachable only from those three containers. All three hold credentials or a client certificate the indexer issued.
    • jackson (request JSON parsing): the same peers, plus anyone logged in to the dashboard, because the dashboard relays their searches to the indexer.
    • jline (the CLI tools) and jsoup: not on the request path.

    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_VERSION stays 4.14 for 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.

  5. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    This is waiting on upstream. Nothing in the repo needs to change.

    • The pinned digest is current: wazuh/wazuh-indexer:4.14.8 (sha256:6a9c1e38…). pin-digests.sh reports no drift, so the tag hasn't been rebuilt since it was pinned.
    • There is no newer release on the registry to move to.
    • The fixed versions exist (table above), but no published image includes them yet. Mostly:
      • 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.Final
      • org.bouncycastle:bcprov-jdk18on: 2 findings, fixed in 1.85
      • com.fasterxml.jackson.core:jackson-core: 2 findings, fixed in 2 different versions (see the table)
      • and 22 more across 17 other packages

    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.

  6. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    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.

    CVE Package (where) What the bug needs What 4.14.8 does Reachable?
    CVE-2026-75595 netty-handler 4.1.135 (transport-netty4, security, ml, performance-analyzer ×2) SNI routing: a SniHandler/SslClientHelloHandler choosing per-SNI SslContexts, where only some require client auth No class in any jar references SniHandler, AbstractSniHandler or SslClientHelloHandler. The security plugin puts one SslHandler per listener, built from opensearch.yml's single ssl.http.* and ssl.transport.* settings. There's no per-SNI context to fall back from. No
    CVE-2026-8763 bcprov-jdk18on 1.84 (security, sql), bcprov-jdk15to18 1.84/1.79 (performance-analyzer), bc-fips 2.1.2 (ml, plugin-cli) A trust chain whose CA carries name constraints (rfc822Name/URI), which a trailing dot then bypasses Every cert trusts root-ca.pem from the Wazuh 4.14 cert tool (CERT_TOOL_VERSION: "4.14"). The tool creates the root with a bare openssl req -x509 -new … -subj '/OU=Wazuh/O=Wazuh/L=California/' and no constraints, and its leaf config has basicConstraints, keyUsage and subjectAltName only. The 4.14 wazuh-certs-tool.sh contains no nameConstraints. There is nothing to bypass. No
    CVE-2025-14813 bcprov-jdk15to18 1.79 (performance-analyzer-rca/lib) Encrypting with BouncyCastle's GOST 28147 CTR mode (G3413CTRBlockCipher) No class outside BouncyCastle references the GOST CTR cipher. The one GOST mention, in the security plugin's cryptacular BlockCipherSpec, 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). No

    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 soc bridge.

    What would change this:

    • Regenerating the CA with name constraints, for example a constrained intermediate.
    • Enabling per-SNI TLS on 9200.
    • A plugin starting to use GOST ciphers.

    None of those is on any plan.

    To reproduce:

    IMG=wazuh/wazuh-indexer:4.14.8@sha256:6a9c1e3827da627a70859213b3e9cfe43193a492e358953de332b94de33b07de
    # copy plugins/ modules/ lib/ performance-analyzer-rca/lib out with `docker create` + `docker cp`, then grep every
    # non-netty/non-BC jar's classes for io/netty/handler/ssl/(Abstract)?SniHandler|SslClientHelloHandler and G3413CTRBlockCipher
    curl -sL https://packages.wazuh.com/4.14/wazuh-certs-tool.sh | grep -nE 'req -x509|nameConstraints'

    🤖 Traced by Claude Code

  7. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Rechecked 2026-10-10. 4.14.8 still resolves to the pinned sha256: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-rc1 with trivy 0.75.0 and scan-images.sh's flags (--image-src remote --platform linux/amd64 --scanners vuln --severity HIGH,CRITICAL --ignore-unfixed):

    4.14.8 (pinned) 5.0.0-rc1
    Critical 6 rows, 3 CVEs 7 rows: netty-handler CVE-2026-75595 (4.1.132 and 4.2.12) and bc-fips CVE-2026-8763 (2.1.2)
    High 46 153: jackson-databind ×35, netty-codec-http ×20, netty-handler ×16, bc-fips ×12, plus netty HTTP/2 and HTTP/3 and httpclient5/httpcore5

    The 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.

  8. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Rechecked 2026-10-10. Upstream is unchanged: 4.14.8 still resolves to the pinned sha256: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.

    • Where: plugins/opensearch-security/lz4-java-1.10.1.jar (trivy 0.75.0 PkgPath).
    • What the bug needs: a local attacker. net.jpountz.util.Native.load() creates an exclusive .lck temp 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 .so before System.load(), giving code execution as the JVM's user.
    • What 4.14.8 does: config/jvm.options sets -Djava.io.tmpdir=${OPENSEARCH_TMPDIR}. bin/opensearch fills that from OpenSearch's TempDirectory launcher, which calls Files.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.

  9. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    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 none container, using javap from the bundled JDK where call sites mattered. None is reachable from the soc bridge.

    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.conf references performance-analyzer-agent, the image has no supervisord binary, and /entrypoint.sh just execs bin/opensearch. (That's from the image; I didn't run ss on odin.)

    CVEs (package) What the bug needs In this image Reachable?
    CVE-2026-55831, -55833, -56745 (netty-codec-http, SPDY) A SPDY codec in a server pipeline No class outside Netty references io/netty/handler/codec/spdy/. No
    CVE-2026-59901 (netty-codec, Bzip2Decoder) A bzip2 decoder on attacker input Nothing references Bzip2Decoder. No
    CVE-2026-56819 (netty-codec-http2) HTTP/2 content decompression (DelegatingDecompressorFrameListener) No HTTP/2 server codec or decompress listener anywhere. codec-http2 is present only in ML and PA. No
    CVE-2026-54399, -54428 (httpcore5, httpcore5-h2) An httpcore5 server, or a client talking to a hostile server ML only, as httpclient5 (client). There's no ServerBootstrap or H2ServerBootstrap. 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. No
    CVE-2026-54512, -54513 (jackson-databind PTV) Polymorphic typing with a PolymorphicTypeValidator No activateDefaultTyping, enableDefaultTyping or PTV use in any plugin. No
    CVE-2026-91776 / -91777 (jackson-databind) @JsonTypeInfo with defaultImpl / @JsonIdentityInfo Neither annotation is used outside Jackson. No
    CVE-2026-68497 (jackson-databind) Jackson binding into javax.xml.datatype.Duration/XMLGregorianCalendar The only classes declaring those types are JAXB, JSON-B (yasson), opencsv and icu4j converters, not Jackson-bound classes. No
    CVE-2026-89407, -89425 (jackson-core) looksLikeValidNumber (databind coercion) / createParser(DataInput) No caller of either outside Jackson. OpenSearch's XContent streams JSON without databind coercion. No
    CVE-2026-13506 (bcprov/bc-fips, ASN.1 nesting guard) BC parsing attacker-supplied ASN.1 The security plugin registers BC with Security.addProvider, i.e. last, so JSSE parses and validates certificates with the JDK provider. BC ASN.1 runs only in parseOtherName/getOtherName for SAN extraction, on certificates that have already chained to our root (clientauth can't skip validation), and in the admin _plugins/_security/api/ssl/certs API on our own certs. No
    CVE-2026-5598 (FrodoEngine timing), -13505 (bc-fips finalizer zeroisation), -8798 (bc-fips RDSEED spin) Post-quantum Frodo KEM / FIPS key lifecycle / failing on-chip entropy Not on the request path: no Frodo use, FIPS isn't enabled, and the last needs a hardware fault. No
    CVE-2026-75140 (jsoup, reports-scheduler) jsoup's XML parser No xmlParser/XmlTreeBuilder use. No
    CVE-2026-77422 (jline-builtins) JLine's interactive grep builtin Only ML's offline explorer CLIs (tribuo, olcut). No
    CVE-2026-106451 (lz4-java) A local user racing the native-library temp file Local only. The container runs one user. No

    This 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:

    • Starting the PA agent, which opens unauthenticated 9600/9650.
    • Configuring an ML remote connector.
    • Enabling HTTP/2 or SPDY on 9200.
    • A plugin turning on Jackson default typing.

    To reproduce:

    IMG=wazuh/wazuh-indexer:4.14.8@sha256:6a9c1e3827da627a70859213b3e9cfe43193a492e358953de332b94de33b07de
    # python3 inside the image (--network none): walk every non-netty/jackson/BC jar's .class bytes for
    #   io/netty/handler/codec/spdy/, Bzip2Decoder, DelegatingDecompressorFrameListener, hc/core5 ServerBootstrap,
    #   activateDefaultTyping|PolymorphicTypeValidator, JsonTypeInfo, JsonIdentityInfo, looksLikeValidNumber, DataInput parser
    docker run --rm --network none --entrypoint sh "$IMG" -c 'command -v supervisord; grep -n "bin/opensearch" /entrypoint.sh; /usr/share/wazuh-indexer/jdk/bin/javap -c -p -cp /usr/share/wazuh-indexer/plugins/opensearch-security/opensearch-security-2.19.6.0.jar org.opensearch.security.OpenSearchSecurityPlugin | grep -E "addProvider|insertProviderAt"'

    🤖 Traced by Claude Code

  10. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    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.

    CVE Rows What the bug needs What runs in this container Reachable?
    CVE-2026-80230 curl-minimal, libcurl-minimal Public-key pinning (--pinnedpubkey / CURLOPT_PINNEDPUBLICKEY) set together with verification turned off. The pin then isn't enforced when the server presents no certificate. curl does run: our healthcheck calls curl -fsk --cert … https://localhost:9200/_cluster/health every 30 s. It turns verification off (-k) but pins nothing. Neither stacks/soc nor stacks/scratch uses --pinnedpubkey. No
    CVE-2026-89161 pcre2, pcre2-syntax A program calling pcre2_jit_match with a previously copied subject passed in as context, on input an attacker controls. /entrypoint.sh runs grep -oP (PCRE) twice at boot, but only over our own config/opensearch.yml. The healthcheck's grep -q '"status"' is a basic regex, not PCRE. The JVM doesn't use pcre2. No: the only PCRE input is our config file
    CVE-2026-78367, CVE-2026-84233 rpm, rpm-libs, rpm-build-libs, rpm-sign-libs, python3-rpm rpmbuild processing a crafted tarball, or rpmuncompress -x on a crafted .gem filename Neither tool is in the image (/usr/bin/rpmbuild and rpmuncompress are absent), and nothing runs rpm after the build No

    What would change this: adding --pinnedpubkey to the healthcheck while keeping -k; an entrypoint that runs grep -P over input we don't write; or a derived image that installs rpm-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:

    IMG=wazuh/wazuh-indexer:4.14.8@sha256:6a9c1e3827da627a70859213b3e9cfe43193a492e358953de332b94de33b07de
    docker run --rm --network none --entrypoint sh "$IMG" -c 'grep -n "grep -oP" /entrypoint.sh; ls /usr/bin/rpmbuild /usr/bin/rpmuncompress /usr/lib/rpm/rpmuncompress'
    git grep -n pinnedpubkey -- stacks/soc stacks/scratch   # nothing

    🤖 Traced by Claude Code

  11. changed the title [-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 46 high)[/-] [+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 69 high)[/+] on Oct 19, 2026
  12. changed the title [-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 69 high)[/-] [+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 84 high)[/+] on Oct 26, 2026
  13. github-actions commented on Oct 26, 2026

    @github-actions
    Author
  14. changed the title [-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 84 high)[/-] [+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 87 high)[/+] on Nov 2, 2026
  15. github-actions commented on Nov 2, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-102554, CVE-2026-108106, CVE-2026-93451.

  16. changed the title [-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 87 high)[/-] [+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 37 high)[/+] on Nov 9, 2026
  17. changed the title [-]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 37 high)[/-] [+]Fixable CVEs in wazuh/wazuh-indexer (6 critical, 71 high)[/+] on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    scratchstacks/scratch on diabolos (VLAN 30)securityA credential, an exposure, or a control that is weaker than recordedsocstacks/soc on odin (VLAN 30)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions