Report · AWS Security BulletinsAbout CVE-2026-121652Published 3 Nov 2026

CVE-2026-121652: Stored cross-site scripting (XSS) in AWS Amplify maplibre-gl-js-amplify popup rendering

Affects maplibre-gl-js-amplifySource AWS Security Bulletins

Compare

Authoritative record:CVE-2026-121652· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 3 Nov 2026, 20:59 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (AMZN)	CVSS 3.1	5.4
CNA (AMZN)	CVSS 4.0	4.8

Affects: web applications using up to 4.0.2

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
npmmaplibre-gl-js-amplify`pkg:npm/maplibre-gl-js-amplify`Other threats	Affected <=4.0.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The vulnerability affects versions up to 4.0.2. The bulletin does not provide explicit patch or remediation details. Until a fix is available, users should consider mitigating risk by sanitizing inputs or limiting use of vulnerable popup and geofence-control features.

Description

CVE-2026-121652 is a stored cross-site scripting (XSS) vulnerability in the AWS Amplify library maplibre-gl-js-amplify, which integrates Amazon Location Service with MapLibre GL JS. The flaw affects popup and geofence-control rendering, allowing malicious scripts to be stored and executed in web applications using versions up to 4.0.2.

Impact

Successful exploitation of this stored XSS vulnerability could allow an attacker to inject malicious scripts that execute in the context of users interacting with affected map popups or geofence controls. This could lead to session hijacking, unauthorized actions, or data theft within the affected web applications. However, no known exploits in the wild have been reported as of the publication date.

Summary

The maplibre-gl-js-amplify library, used for rendering maps and geofencing controls in web applications, contains a stored XSS vulnerability (CVE-2026-121652) in its popup and geofence-control rendering components. This vulnerability affects all versions up to and including 4.0.2. The issue was identified by AWS and publicly disclosed in an AWS Security Bulletin dated November 3, 2026. No further technical details or exploit code are provided in the bulletin.

References

aws.amazon.com/security/security-bulletins/rss/2026-167-aws/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 19:31 UTC

Technical details

References

Community reviews

Related threats