EUVD-2026-119758
GHSA-rw6v-c2pc-5g8v
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed moto_server Batch endpoint
-
DeliverySubmit crafted Batch job request
-
ExploitManipulate privileged/volumes arguments
-
ExecutionEmulation mishandles privilege settings
-
ImpactAlter mocked container state
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
|
| Exploitation Conditions | Exploitation requires moto to be deployed in its network-accessible moto_server mode with the AWS Batch emulation endpoint reachable, and specifically targets the privileged and volumes arguments handled in moto/batch/models.py. The dominant limiting factor is deployment mode: moto is normally used as an in-process mocking library inside test suites and CI pipelines, where there is no remote network surface at all; only the optional standalone moto_server exposes HTTP endpoints. Impact is further bounded because the affected component emulates AWS Batch rather than controlling a real AWS account, so effects are limited to the mocked/emulated state. |
| Impact | The signals point to a low real-world priority despite a medium CVSS 4.0 score of 5.5. moto is a Python library that mocks/emulates AWS services for automated testing, so the affected 'AWS Batch Emulation' is a test double rather than a production control plane - improper handling of the privileged/volumes arguments (CWE-266) affects emulated state, not a real AWS environment. The CVSS 4.0 vector claims AV:N/AC:L/PR:N/UI:N with low confidentiality, integrity and availability impact, and E:P marks a proof-of-concept maturity; however, moto is most commonly imported as an in-process library (local, no network surface), and network reachability only exists if the optional moto_server HTTP mode is exposed - so the AV:N rating realistically applies only to that deployment mode, which should be verified. There is no CISA KEV listing and no EPSS score in the provided data, so there is no evidence of widespread or targeted active exploitation. The single intelligence source is VulDB (cna@vuldb.com), the vendor did not respond to disclosure, and NVD references carry no titles, so corroboration is weak. Net assessment: a genuinely low-impact issue in test tooling that is unlikely to warrant emergency action; the vuln.today 'this_month' decision label is consistent with routine, non-urgent remediation. |
| Exploit ScenarioDerived | If an organization runs moto in its network-exposed moto_server mode, a remote actor reaching the AWS Batch mock endpoint could submit a request manipulating the privileged/volumes parameters so the emulation improperly grants privileged container settings, skewing the mocked Batch job state. A public proof-of-concept is referenced (a Google Drive link), but it is not verified as working exploit code. In the far more common in-process library usage there is no remote attack surface at all. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 09, 2026
Improper privilege management in moto's AWS Batch emulation component (moto/batch/models.py) affects releases up to and including 5.2.4, where manipulation of the 'privileged' and 'volumes' arguments lets a remote caller obtain a privilege level the emulated resource should not grant. Unauthenticated remote exploitation over HTTP is possible only when moto is run in its optional standalone moto_server mode with the AWS Batch endpoint reachable; the far more common in-process library deployment used inside test suites and CI pipelines exposes no network surface at all. Impact is bounded because the affected code emulates AWS Batch rather than controlling a real AWS account, so effects are confined to mocked state; the advisory states exploit material has been made public, though no independent confirmation of working exploit code is available, and the vendor did not respond to the disclosure.
RemediationAI
No vendor-released patch was identified at time of analysis and the maintainers did not respond to the disclosure, so no fixed version number can be cited; teams that rely on moto_server should treat versions up to and including 5.2.4 as unpatched and track the upstream project for a release that validates or rejects the privileged and volumes arguments in moto/batch/models.py. The most effective mitigation is to avoid the network-exposed deployment mode: run moto as an in-process mocking library rather than starting moto_server, which removes the remote attack surface entirely at the cost of losing cross-process or cross-language test clients. Where a shared moto_server instance is required, bind it to a loopback or test-only interface and firewall the listener so only trusted CI runners can reach it, and keep it off any host that also holds real credentials or reachable production metadata services; the trade-off is that shared developer or QA access must be routed through the permitted hosts. Because the flaw is in emulation code, the impact stays inside mocked state, so isolating the emulator from real AWS credentials and real IAM roles further caps what a permissive Batch job definition can achieve. Review any test or pipeline configuration that passes privileged=true or attaches host volumes to emulated Batch jobs and strip those arguments until a corrected release is adopted.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
moto is a Python library that mocks AWS service APIs so tests can exercise boto3 code without touching real cloud accounts. The affected module, moto/batch/models.py, implements the AWS Batch emulation backend, whose job-definition submission path accepts a 'privileged' flag and a 'volumes' list mirroring the real container properties of an AWS Batch job definition. The flaw is classified as CWE-266 (Incorrect Privilege Assignment): the emulation accepts and applies these caller-supplied arguments without enforcing the privilege boundary the equivalent real service enforces, so a request that should be rejected or constrained is honoured. The trigger path is a network request handled by the optional moto_server HTTP front end; when moto is imported directly as a mocking library there is no HTTP listener and no remote attack surface, which is the dominant limiting factor on real-world exposure. The CVSS 4.0 vector carries AV:N/AC:L/AT:N/PR:N/UI:N with only low confidentiality, integrity and availability impact and no subsequent-system impact (SC:N/SI:N/SA:N), and the E:P metric reflects the reported public exploit material rather than observed exploitation. No CPE strings were supplied with the record, so exact affected package builds beyond the stated 'up to 5.2.4' range are not confirmed from the available data.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
AV:N and PR:N apply only to the unauthenticated moto_server HTTP mode; impacts are low because the flaw affects emulated Batch state, not a real AWS environment.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
DescriptionCVE.org
A weakness has been identified in Tidelift moto up to 5.2.4. Affected is an unknown function of the file moto/batch/models.py of the component AWS Batch Emulation. This manipulation of the argument privileged/volumes causes improper privilege management. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
NVD
CVE.org
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Exploit-DB