Skip to content
Heist/ feed
Back to feed
Medium

Wazuh has Stack-Based Buffer Overflow in Security Configuration Assessment JSON Parser

Type: advisorySources: OSV

Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 3.9.0 and prior to version 4.14.3, multiple stack-based buffer overflows exist in the Security Configuration Assessment (SCA) decoder (`wazuh-analysisd`). The use of `sprintf` with a floating-point (`%lf`) format specifier on a fixed-size 128-byte buffer allows a remote attacker to overflow the stack. A specially crafted JSON event can trigger this overflow, leading to a denial of service (crash) or potential RCE on the Wazuh manager. The vulnerability is located in `/src/analysisd/decoders/security_configuration_assessment.c`, within the `FillScanInfo` and `FillCheckEventInfo` functions. In multiple locations, a 128-byte buffer (`char value[OS_SIZE_128];`) is allocated on the stack to hold the string representation of a number from a JSON event. The code checks if the number is an integer or a double. If it's a double, it uses `sprintf(value, "%lf", ...)` to perform the conversion. This `sprintf` call is unbounded. If a floating-point number with a large exponent (e.g., `1.0e150`) is provided, `sprintf` will attempt to write its full string representation (a "1" followed by 150 zeros), which is larger than the 128-byte buffer, corrupting the stack. Version 4.14.3 patches the issue.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-25790
Confirmed fixed CVEs
Not specified
Updated in this feed
2 Nov 2026, 21:06 UTC · Revision 1

Source evidence

Wazuh has Stack-Based Buffer Overflow in Security Configuration Assessment JSON Parser

core-osv · Original source

Published 17 Mar 2026, 18:41 UTC

Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 3.9.0 and prior to version 4.14.3, multiple stack-based buffer overflows exist in the Security Configuration Assessment (SCA) decoder (`wazuh-analysisd`). The use of `sprintf` with a floating-point (`%lf`) format specifier on a fixed-size 128-byte buffer allows a remote attacker to overflow the stack. A specially crafted JSON event can trigger this overflow, leading to a denial of service (crash) or potential RCE on the Wazuh manager. The vulnerability is located in `/src/analysisd/decoders/security_configuration_assessment.c`, within the `FillScanInfo` and `FillCheckEventInfo` functions. In multiple locations, a 128-byte buffer (`char value[OS_SIZE_128];`) is allocated on the stack to hold the string representation of a number from a JSON event. The code checks if the number is an integer or a double. If it's a double, it uses `sprintf(value, "%lf", ...)` to perform the conversion. This `sprintf` call is unbounded. If a floating-point number with a large exponent (e.g., `1.0e150`) is provided, `sprintf` will attempt to write its full string representation (a "1" followed by 150 zeros), which is larger than the 128-byte buffer, corrupting the stack. Version 4.14.3 patches the issue.

osv:CVE-2026-25790
Complete source record
{
  "id": "60736eabeaf3314806667b47fcbc01891d17c51b15bed3bed85a18a2dc9c453a",
  "url": "https://osv.dev/vulnerability/CVE-2026-25790",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Wazuh has Stack-Based Buffer Overflow in Security Configuration Assessment JSON Parser",
    "summary": "Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 3.9.0 and prior to version 4.14.3, multiple stack-based buffer overflows exist in the Security Configuration Assessment (SCA) decoder (`wazuh-analysisd`). The use of `sprintf` with a floating-point (`%lf`) format specifier on a fixed-size 128-byte buffer allows a remote attacker to overflow the stack. A specially crafted JSON event can trigger this overflow, leading to a denial of service (crash) or potential RCE on the Wazuh manager. The vulnerability is located in `/src/analysisd/decoders/security_configuration_assessment.c`, within the `FillScanInfo` and `FillCheckEventInfo` functions. In multiple locations, a 128-byte buffer (`char value[OS_SIZE_128];`) is allocated on the stack to hold the string representation of a number from a JSON event. The code checks if the number is an integer or a double. If it's a double, it uses `sprintf(value, \"%lf\", ...)` to perform the conversion. This `sprintf` call is unbounded. If a floating-point number with a large exponent (e.g., `1.0e150`) is provided, `sprintf` will attempt to write its full string representation (a \"1\" followed by 150 zeros), which is larger than the 128-byte buffer, corrupting the stack. Version 4.14.3 patches the issue.",
    "evidence": "osv:CVE-2026-25790",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2026-25790",
      "aliases": [
        "CVE-2026-25790",
        "GHSA-cf24-hq8x-5jx2"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/wazuh/wazuh",
              "type": "GIT",
              "events": [
                {
                  "introduced": "18bac2de69f5a37e5c3c4e2dfbce5a0093042ea7"
                },
                {
                  "fixed": "b6b6e94a432f7a3e20d1eea1c58ebd01d2d30999"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "3.9.0"
                      },
                      {
                        "fixed": "4.14.3"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StringRangeExpression"
                  },
                  {
                    "cpe": "cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "3.9.0"
                      },
                      {
                        "fixed": "4.14.3"
                      }
                    ],
                    "source": "CPE_RANGE"
                  }
                ]
              }
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-25790.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:23.749851567Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/25xxx/CVE-2026-25790.json",
        "https://github.com/wazuh/wazuh/security/advisories/GHSA-cf24-hq8x-5jx2",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-25790"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-121",
          "CWE-787"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/25xxx/CVE-2026-25790.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-25790",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 490065,
  "published_at": "2026-03-17T18:41:45.834+00:00"
}