Skip to main content
Menu
CVEs

CVE

SamWaf request inspection bypass in WAF via chunked bodies

CVE-2026-129869EUVD-2026-126451

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

6.9MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
32/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

The SamWaf WAF from samwafgo can be bypassed by a remote attacker without logging in. By sending requests with chunked encoding or bodies of 2048 bytes or more, the attacker can get SQL injection, XSS, command injection, path traversal, or file upload payloads past inspection and onto the protected backend.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

SamWaf 1.0.128 through 1.3.25-beta.11 contains a request body inspection bypass vulnerability in WafEngine.ServeHTTP that skips bodies with chunked encoding or lengths of 2048 bytes or more. Remote unauthenticated attackers can send SQL injection, XSS, command injection, traversal or upload payloads chunked or padded, which reach the protected backend uninspected.

cve.now Index

32Pcve.now Index 32 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129869 (SamWaf 1.0.128 through 1.3.25-beta.11 WAF Bypass via Chunked or Oversized Request Body), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129869 (entry last updated 2026-11-16):
Affected:
- samwafgo SamWaf: from 1.0.128, through 1.3.25-beta.11
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129869 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129869 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/samwafgo/SamWaf/issues/1063
- https://vul.yulun.ac.cn/20261116/samwaf/
- https://github.com/samwafgo/SamWaf/blob/23bb891eea44d24b7242de97462b35f91e64cbfe/wafenginecore/wafengine.go#L270-L292
- https://github.com/samwafgo/SamWaf/blob/23bb891eea44d24b7242de97462b35f91e64cbfe/wafenginecore/wafengine.go#L1428-L1435
- https://www.vulncheck.com/advisories/samwaf-1.0.128-through-1.3.25-beta.11-waf-bypass-via-chunked-or-oversized-request-body
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129869
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129869"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • samwafgo SamWaf

    From 1.0.128 · through 1.3.25-beta.11

Evidence 7

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Report
  2. Repository
  3. Repository
  4. Link
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129869

Is CVE-2026-129869 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129869?

SamWaf: from 1.0.128 through 1.3.25-beta.11.Source: cve.now feed data