Fallos del tipo CWE-416

5126 resultados

Uso após liberação de memória

Ocorre quando o código tenta acessar uma área de memória que já foi liberada (deallocated). O programa continua usando um ponteiro que aponta para um endereço inválido, causando leitura/escrita em memória não controlada. Isso pode levar a crash, corrupção de dados ou execução arbitrária de código.

Ejemplo

Um navegador aloca memória para um objeto DOM, depois o remove da página e libera a memória. Se um script JavaScript ainda tentar acessar esse objeto deletado, o navegador tenta ler/escrever em um endereço que agora contém outro dado, causando comportamento impredizível ou exploração por atacante.

Cómo mitigar

Use linguagens com garbage collection (Java, Python, C#) ou práticas rigorosas: null os ponteiros após free(), use smart pointers (C++), evite compartilhamento de referências sem sincronização, faça testes de memória com ferramentas como Valgrind ou AddressSanitizer.

CVE-2024-23158HIGHMultiple ZDI Vulnerabilities in Autodesk AutoCAD and certain AutoCAD-based productsEPSS 0.4%CVE-2025-52886MEDIUMPoppler Use After Free VulnerabilityEPSS 0.4%CVE-2023-51549HIGHFoxit PDF Reader AcroForm Doc Object Use-After-Free Remote Code Execution VulnerabilityEPSS 0.4%CVE-2026-4390MEDIUMTeamSpeak 3 Server Connection State Management process_resend_queue use after freeEPSS 0.4%CVE-2025-62205HIGHMicrosoft Office Remote Code Execution VulnerabilityEPSS 0.4%CVE-2026-68843MEDIUMMicrosoft Office Word Information Disclosure VulnerabilityEPSS 0.4%CVE-2025-62216HIGHMicrosoft Office Remote Code Execution VulnerabilityEPSS 0.4%CVE-2026-93374CRITICALUse after free in Dawn in Google Chrome on on Android prior to 153.0.8010.52 allowed a remote attacker to potentially execute arbitrary codeEPSS 0.4%CVE-2026-6315HIGHUse after free in Permissions in Google Chrome on Android prior to 147.0.7727.101 allowed a remote attacker who convinced a user to engage iEPSS 0.4%CVE-2026-9883HIGHUse after free in Base in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code via a crafted HTML page.EPSS 0.4%CVE-2026-76021HIGHUse after free in DOM in Google Chrome prior to 151.0.7922.173 allowed a remote attacker to execute arbitrary code inside the sandbox via a EPSS 0.4%CVE-2026-5872HIGHUse after free in Blink in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to execute arbitrary code inside a sandbox via a cEPSS 0.4%CVE-2026-5866HIGHUse after free in Media in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to execute arbitrary code inside a sandbox via a cEPSS 0.4%CVE-2026-17661HIGHUse after free in Loader in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to execute arbitrary code inside a sandbox via a EPSS 0.4%CVE-2026-79097HIGHUse after free in V8 in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crEPSS 0.4%CVE-2026-87460HIGHUse after free in Platform in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox viEPSS 0.4%CVE-2026-6317HIGHUse after free in Cast in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbitrary code via a crafted HTML page.EPSS 0.4%CVE-2026-16805HIGHUse after free in Blink in Google Chrome prior to 150.0.7871.186 allowed a remote attacker to execute arbitrary code inside a sandbox via a EPSS 0.4%CVE-2026-15126HIGHUse after free in Forms in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to execute arbitrary code inside a sandbox via a EPSS 0.4%CVE-2026-78899HIGHUse after free in V8 in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crEPSS 0.4%