opsli-boot denial of service in WAF request wrapper
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
hiparker opsli-boot is affected by a denial-of-service flaw in its WAF Plugin, in the getInputStream function of WafHttpServletRequestWrapper.java. An attacker can disrupt the service remotely over the network, without logging in or any user action.
Written by a model
Original description
A vulnerability was found in hiparker opsli-boot up to 2.2.1. This affects the function getInputStream of the file opsli-plugins/opsli-plugins-waf/src/main/java/org/opsli/plugins/waf/servlet/WafHttpServletRequestWrapper.java of the component WAF Plugin. The manipulation results in denial of service. The attack can be executed remotely.
What to do
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-133601 (hiparker opsli-boot WAF Plugin WafHttpServletRequestWrapper.java getInputStream denial of service), 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-133601 (entry last updated 2026-11-20):
Affected:
- hiparker opsli-boot: versions 2.2.0, 2.2.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133601 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133601 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/hiparker/opsli-boot/issues/48
- https://vuldb.com/vuln/441037
- https://vuldb.com/vuln/441037/cti
- https://vuldb.com/cve/CVE-2026-133601
- https://vuldb.com/submit/1050067
- https://github.com/hiparker/opsli-boot/
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-133601
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-133601"}.Affected versions
- hiparker opsli-boot2.2.0, 2.2.1
cve.now Index
- 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
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133601 |
| Record | NVD · CVE-2026-133601 |
| Other links 6 | |
| Advisory | VulDB · Advisory #441037 |
| Advisory | VulDB · Threat intelligence #441037 |
| Advisory | VulDB · CVE-2026-133601 record |
| Advisory | VulDB · Submission #1050067 |
| Report | GitHub · hiparker/opsli-boot · Issue #48 |
| Repository | GitHub · hiparker/opsli-boot · Repository |
Questions about CVE-2026-133601
Is CVE-2026-133601 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-133601?
opsli-boot: versions 2.2.0, 2.2.1.
Source: cve.now feed data
Related
- CVE-2026-132140DrayTek Vigor2960 Apmcfg Upload mainfunction.cgi null pointer dereference
- CVE-2026-49785UEFI Secure Boot Security Feature Bypass Vulnerability
- CVE-2026-133608OpenZipkin HTTP Collector ZipkinHttpCollector.java UnzippingBytesRequestConverter.convertRequest data amplification
- CVE-2026-133606PowerJob CachingRequestBodyFilter CachingRequestBodyFilter.java CustomHttpServletRequestWrapper denial of service
- CVE-2026-33275Improper resource shutdown or release for some Intel(R) PROSet/Wireless Wi-Fi Software for Windows within Ring 3: User Applications may…
- CVE-2026-128018FrankenPHP before 1.13.4 Pending Worker Request Denial of Service
No corrections so far. Something wrong on this page? Report an error.