CVE-2025-53022
HighSummary
Podatność w TrustedFirmware-M przed wersją 2.1.3 oraz 2.2.x przed 2.2.1 polega na braku walidacji długości podczas aktualizacji oprogramowania. Moduł aktualizacji oprogramowania nie sprawdza, czy długość pola w strukturze Type-Length-Value (TLV) dla komponentów zależnych nie przekracza maksymalnego dozwolonego rozmiaru, co może prowadzić do nadpisania pamięci stosu.
Risk Assessment
Atakujący może wykorzystać tę podatność, tworząc złośliwy wpis TLV w niechronionej sekcji obrazu aktualizacji MCUBoot, co może prowadzić do manipulacji pamięcią stosu systemu. To stwarza ryzyko destabilizacji systemu oraz potencjalnego przejęcia kontroli nad nim.
Recommendation
Zaleca się aktualizację TrustedFirmware-M do wersji 2.1.3 lub 2.2.1 i monitorowanie wszelkich aktualizacji bezpieczeństwa, aby zminimalizować ryzyko związane z tą podatnością.
Related vulnerabilities
- CVE-2026-96891Critical
A vulnerability was identified in D-Link DIR-825 3.00b32 in the tunnel_set_params function of tunnel.c in the rp-l2tp component. Manipulation of the peer_hostname argument leads to an out-of-bounds write. The attack may be initiated remotely.
- CVE-2026-18467Critical
The Paytium: Mollie payment forms & donations plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.0.3. The 5.0.3 patch added a signature gate on the pt-paytium-user-data field but left a second filter, pt_cf_checkout_meta(), that copies $_POST['pt_form_field'] values without signature verification, allowing the user role to be overwritten and an administrator account to be created.
- CVE-2026-93577Critical
GitLab CE/EE versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 contain an integer overflow issue when compiling a specially crafted regular expression in a CI/CD configuration. Under certain conditions an authenticated user could execute arbitrary code on the GitLab server.
- CVE-2026-89078Critical
GitLab CE/EE versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 contain a double free issue when parsing a specially crafted regular expression in a CI/CD configuration. Under certain conditions an authenticated user could execute arbitrary code on the GitLab server.
- CVE-2026-93352Critical
Laravel-Mediable versions 7.0.0 to 7.0.2 contain an incomplete patch for CVE-2026-49972 — the .pht extension is missing from the forbidden_extensions blocklist in config/mediable.php. Apache on Debian and Ubuntu executes .pht files as PHP, allowing an attacker to upload a malicious file and achieve remote code execution.
- CVE-2026-6928Critical
IBM Concert versions 1.0.0 through 3.0.0 references or accesses memory after it has been freed (use-after-free). An attacker who can influence program execution or input may exploit this condition to corrupt memory, cause application crashes, or execute arbitrary code.
- CVE-2026-6730Critical
IBM Concert versions 1.0.0 through 3.0.0 is vulnerable to a buffer overflow caused by improper bounds checking. A local user could overflow the buffer and execute arbitrary code on the system.
- CVE-2026-6721Critical
IBM Concert versions 1.0.0 through 3.0.0 allows an unauthenticated remote attacker to supply specially crafted input that is incorporated into OS commands, resulting in arbitrary command execution. Successful exploitation allows remote code execution with the privileges of the affected application.
- CVE-2026-67404Critical
RabbitMQ prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 — when no CA bundle is available, ssl_options/1 falls back to [{verify, verify_none}] with no warning. An attacker in a man-in-the-middle position can forge the JWKS response, leading the broker to accept arbitrary JWTs.
- CVE-2026-67231Critical
RabbitMQ prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 — the trust-store plugin installs a verify_fun that overrides {bad_cert, unknown_ca} / {bad_cert, selfsigned_peer} when the presented cert "matches" a whitelisted one. The match key relies solely on issuer name and serial number, which can be easily forged, allowing TLS client authentication bypass.
Original NVD description (English source)
TrustedFirmware-M (aka Trusted Firmware for M profile Arm CPUs) before 2.1.3 and 2.2.x before 2.2.1 lacks length validation during a firmware upgrade. While processing a new image, the Firmware Upgrade (FWU) module does not validate the length field of the Type-Length-Value (TLV) structure for dependent components against the maximum allowed size. If the length specified in the TLV exceeds the size of the buffer allocated on the stack, the FWU module will overwrite the buffer (and potentially other stack data) with the TLV's value content. An attacker could exploit this by crafting a malicious TLV entry in the unprotected section of the MCUBoot upgrade image. By setting the length field to exceed the expected structure size, the attacker can manipulate the stack memory of the system during the upgrade process.

