PULSE
FEED
ransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomn0n reclama a Exelixis, Inc. · US · Healthcareransomn0n reclama a BeOne Medicines Ltd. (BeiGene) · US · Healthcareransomn0n reclama a Azurity Pharmaceuticals, Inc. · US · Healthcareransomn0n reclama a D.R. Johnson Financial · CA · Financial Servicesransomn0n reclama a Arca Financial Group · CA · Financial Servicesransomn0n reclama a ARCA Financial · CA · Financial Servicesransomn0n reclama a Pearl Planning · CA · Professional Servicesransomn0n reclama a Wise Advisory Group · CA · Professional Servicesransomn0n reclama a The ODP Corporation (Office Depot) · US · Retail & E-Commerceransomn0n reclama a Networth Management · CA · Financial Servicesransomn0n reclama a Visa Inc. · US · Financial Servicesransomn0n reclama a Mastercard Incorporated · US · Financial Servicesransommetaencryptor reclama a SRM Technologies · US · Technologyransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomn0n reclama a Exelixis, Inc. · US · Healthcareransomn0n reclama a BeOne Medicines Ltd. (BeiGene) · US · Healthcareransomn0n reclama a Azurity Pharmaceuticals, Inc. · US · Healthcareransomn0n reclama a D.R. Johnson Financial · CA · Financial Servicesransomn0n reclama a Arca Financial Group · CA · Financial Servicesransomn0n reclama a ARCA Financial · CA · Financial Servicesransomn0n reclama a Pearl Planning · CA · Professional Servicesransomn0n reclama a Wise Advisory Group · CA · Professional Servicesransomn0n reclama a The ODP Corporation (Office Depot) · US · Retail & E-Commerceransomn0n reclama a Networth Management · CA · Financial Servicesransomn0n reclama a Visa Inc. · US · Financial Servicesransomn0n reclama a Mastercard Incorporated · US · Financial Servicesransommetaencryptor reclama a SRM Technologies · US · Technology
← Todos os CVEs
CVE Watch14 de out. de 2026

CVE-2022-40304

An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading t

CVSS

7.8

Alta

EPSS

5.8%

p93

KEV

—

Exploit Today

28

0-100

Publicado: 23 de nov. de 2022 · Última mod.: 14 de out. de 2026 · CWE-415

EPSS · 30d
5.8%EPSS · 30 dias5.8%
2026-10-182026-11-15
Descrição técnica

An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-129456—
19.0%
——6In FRRouting, bgpd frees the sub-TLV chain of a Tunnel Encapsulation attribute (type 23) while routes stored by bgpd still point to it, if the attribute is received from a neighbor that has "soft-reconfiguration inbound" configured. A cache added to speed up attribute interning while processing the prefixes of an UPDATE checks whether an interned attribute set may be reused by comparing the parsed attributes with themselves, so the check always succeeds. Interning the parsed attributes for the Adj-RIB-In removes the Tunnel Encapsulation sub-TLVs from them, and the copy that bgpd then interns for the route reuses the cached attribute set, which still holds the sub-TLVs, without taking a reference on them. When the route is later replaced, withdrawn or cleared, for example when the session goes down, the sub-TLV chain is freed while still in use, and bgpd then reads it, decrements a reference count inside it and frees it a second time. In the reporter's build without AddressSanitizer this ended in an assertion failure in bgpd's memory accounting, aborting bgpd and dropping all BGP sessions on the router, and the neighbor can repeat it each time bgpd restarts. Because freed heap memory is written to and freed again, consequences beyond a crash cannot be ruled out. An established BGP session is required, and the attribute does not need to be malformed. bgpd processes attribute 23 from every neighbor, including eBGP neighbors, unless it is explicitly discarded, although RFC 9012 requires it to be filtered on eBGP sessions by default. Neighbors without "soft-reconfiguration inbound" are not affected.23h
CVE-2026-120221—
20.3%
——6In FRRouting, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a "bgp listen range" also has a Site-of-Origin configured ("neighbor PG soo"). Each dynamic neighbor shares the peer-group's SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. The first disconnect leaves the peer-group pointing at freed memory, and the second disconnect frees it again, causing bgpd to abort and drop all BGP sessions on the router. Any host whose address falls inside the listen range can trigger this by opening and closing two TCP connections to the BGP port, without sending any BGP message and without knowing the AS number, and can repeat it each time bgpd restarts. If the peer-group has a TCP-MD5 password, only hosts that know the password can trigger it. Two ordinary flaps of legitimate dynamic neighbors have the same effect. Between the two frees, displaying the configuration ("show running-config") or establishing a dynamic neighbor also reads the freed memory, which can crash bgpd after a single disconnect. Only configurations that combine a listen range with a SoO on the same peer-group are affected.2d
CVE-2026-1280173.7 BAI
44.7%
——13FrankenPHP before 1.13.4 contains a double free vulnerability in worker mode that frees SG(request_info).content_type_dup twice when a worker script ends its loop after a non-form POST request. Unauthenticated attackers can send repeated JSON POST requests until the worker loop ends, aborting the whole process when USE_ZEND_ALLOC=0 is set.3d
CVE-2026-1002903.7 BAI
27.4%
——8The regcomp and regexec functions in the GNU C Library version 2.3 to version 2.44 may read freed memory and free the same heap block twice when a memory allocation fails while a regular expression is compiled or matched. The re_dfa_add_node (the NFA node table) and build_range_exp (bracket ranges) grow several arrays with consecutive realloc calls and store the new pointers only after all of them succeed. When a later call fails, the pattern buffer keeps pointers to blocks that were already freed, and the error cleanup frees them again. In regexec, the back-reference cache (match_ctx_add_entry) frees its array when a realloc fails but keeps the pointer, which is freed again on the error path. An attacker does not need to supply a crafted regular expression: patterns large enough to grow these arrays are common. The failure has to hit a specific allocation, though, so the issue can only be reached when the system is already under memory pressure. An attacker who supplies the pattern or the subject string has little control over which allocation fails, so the expected impact is a crash of the process. This issue affects all architectures and ABIs supported by the GNU C Library.4d
CVE-2026-569719.8 CRÍ
25.4%
——8In AudioSession::SendInternalEvent of AudioSession.cpp, there is a possible Double Free due to a logic error in the code. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.3d
CVE-2026-969697.0 ALT
21.4%
——6Double free in Windows TCP/IP allows an authorized attacker to elevate privileges locally.6d