Improper validation in meraki
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Improper validation made it possible for an attacker to modify the HTTP request (e.g. to insert a new header) or create a new HTTP request if the attacker controls the HTTP version. The vulnerability only occurs if the attacker can control the HTTP version of the request. This issue has been patched in version 3.9.0. meraki from version 1.40.1 requires aiohttp 3.9.0
Why it matters now
Fix Fixed meraki (PyPI): 1.40.1
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | meraki (PyPI) | before 1.40.1 | 1.40.1 | Patch available | GHSA-6x4h-9622-fqr6 |
- meraki (PyPI) Vendor— Affected before 1.40.1 Fixed in 1.40.1 Patch available GHSA-6x4h-9622-fqr6
Remediation
- Fix · GHSA-6x4h-9622-fqr6 meraki (PyPI) Fixed in 1.40.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-6x4h-9622-fqr6
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences