samwafgo SamWaf up to 1.3.25-beta.11 Request Body Inspection WafEngine.ServeHTTP input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.26+ |
Summary
A vulnerability described as critical has been identified in samwafgo SamWaf up to 1.3.25-beta.11. Affected is the function WafEngine.ServeHTTP of the component Request Body Inspection. Executing a manipulation can lead to input validation.
This vulnerability is tracked as CVE-2026-129869. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in samwafgo SamWaf up to 1.3.25-beta.11. It has been declared as critical. This vulnerability affects the function WafEngine.ServeHTTP of the component Request Body Inspection. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-129869 since 11/16/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 11/16/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 1.3.25-beta.0
- 1.3.25-beta.1
- 1.3.25-beta.2
- 1.3.25-beta.3
- 1.3.25-beta.4
- 1.3.25-beta.5
- 1.3.25-beta.6
- 1.3.25-beta.7
- 1.3.25-beta.8
- 1.3.25-beta.9
- 1.3.25-beta.10
- 1.3.25-beta.11
Website
- Product: https://github.com/samwafgo/SamWaf/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/16/2026 Advisory disclosed11/16/2026 CVE reserved
11/16/2026 VulDB entry created
11/16/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CNA: VulnCheck
CVE: CVE-2026-129869 (🔒)
GCVE (CVE): GCVE-0-2026-129869
GCVE (VulDB): GCVE-100-437722
Entry
Created: 11/16/2026 16:00Changes: 11/16/2026 16:00 (75)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.