Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
céu pouco nublado

18 ℃

58%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 14:30:01

[USD] USD 62,313.36

[BRL] BRL 323,506.02 [USD] USD 62,313.36 [GBP] GBP 47,104.60 [EUR] EUR 54,314.07
Price index provided by blockchain.info.
After Bitcoin Core 0.14.0 and before Bitcoin Core 29.0, validating a specially-crafted block may cause the node to access previously freed memory.
During validation, necessary data required for checking inputs for each transaction is pre-calculated and cached. For specially crafted invalid blocks, it was possible for this data to be destroyed while it was still being accessed by a background validation thread. An attacker capable of mining a block with sufficient proof-of-work could have exploited this to crash victim nodes. Because of the nature of use-after-free bugs, it is possible that the crash could have been used for remote code execution, though constraints on the input (block) data make this unlikely.
This issue is considered High severity.

Details
By default, script validation for new blocks is dispatched to background threads via a vector of CScriptCheck functors. Each CScriptCheck holds a pointer to a PrecomputedTransactionData object which stores some data needed by each input in the transaction. Because it stores a pointer and not the data itself, care must be taken to ensure that the PrecomputedTransactionData outlives the CScriptCheck.
The script checks lifetime is enforced by an RAII class, CCheckQueueControl. However, the control is intantiated before the precomputed transaction data. Because local objects in C++ are destructed in reverse order of construction, this means the vector of PrecomputedTransactionData is destroyed before the CCheckQueueControl.
This is not an issue when the block is valid, as CCheckQueueControl::Wait() will be called before the function returns and the PrecomputedTransactionData gets destroyed. However, in case of an early return (when a separate check fails) a background script thread may read the precomputed transaction data after it was destroyed. An attacker could exploit this to crash victim nodes at the expense of a valid PoW at tip.

Attribution
Cory Fields (MIT DCI) discovered this vulnerability and responsibly disclosed it in a detailed report containing a proof of concept for reproduction and a proposed mitigation.

Timeline
- 2024-11-02 Cory Fields privately reports the bug
- 2024-11-06 Pieter Wuille pushes a covert fix to already open PR #31112 which works around the issue by removing the early returns
- 2024-12-03 PR #31112 is merged
- 2025-04-12 Bitcoin Core version 29.0 is released with a fix
- 2026-04-19 The last vulnerable Bitcoin Core version (28.x) goes end of life
- 2026-05-05 Public disclosure.

dog - 14:56:48 up 271 days, 23:28, 5 users, load average: 0.00, 0.00, 0.00

[18/06/2026 12:22] Flávio Bolsonaro cita operação contra Jaques Wagner durante lançamento de plano de segurança - G1

[18/06/2026 07:13] Deputado estadual Val Ceasa é alvo de buscas em operação contra ligação de agentes públicos com o TCP - G1

[17/06/2026 22:06] Motta pediu a Vorcaro empréstimo de R$ 22 mi para cunhada, diz jornal - Poder360

[18/06/2026 11:34] Rússia ameaça Ucrânia com ataques regulares "em grande escala" - CNN Brasil

[18/06/2026 07:08] Eduardo publica foto de Moraes ao lado de vilão de Harry Potter - Poder360

[17/06/2026 19:46] Estados Unidos e Irã assinam acordo de paz para encerrar guerra - Correio Braziliense

[18/06/2026 09:29] Repórter da Record tropeça na beira da ponte onde jovem morreu após salto sem corda e quase cai; veja vídeo - Jornal Correio

[18/06/2026 11:42] "Não foi acidente", diz pai de youtuber morto em queda de helicóptero no RJ - CNN Brasil

[18/06/2026 08:19] JERÔNIMO RODRIGUES ANTECIPA SALÁRIO DE SERVIDORES PARA O SÃO JOÃO - - Bahia Economica

[18/06/2026 09:30] Daniela Lima: Rivais fecham reação a plano 'tiro, porrada e bomba' de Flávio na segurança - UOL Notícias

[CVE-2025-33236] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework contains a vulnerability where malicious data created by an attacker could cause code injection. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

[CVE-2025-33239] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA Megatron Bridge contains a vulnerability in a data merging tutorial, where malicious input could cause a code injection. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

[CVE-2025-33240] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA Megatron Bridge contains a vulnerability in a data shuffling tutorial, where malicious input could cause a code injection. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

[CVE-2025-33241] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution by loading a maliciously crafted file. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

[CVE-2025-33243] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution in distributed environments. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

[CVE-2025-33245] [Modified: 17-06-2026] [Analyzed] [V3.1 S8.0:HIGH] NVIDIA NeMo Framework contains a vulnerability where malicious data could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

[CVE-2025-33246] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework for all platforms contains a vulnerability in the ASR Evaluator utility, where a user could cause a command injection by supplying crafted input to a configuration parameter. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, or information disclosure.

[CVE-2025-33249] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework for all platforms contains a vulnerability in a voice-preprocessing script, where malicious input created by an attacker could cause a code injection. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

[CVE-2025-33250] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.

[CVE-2025-33251] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.

[CVE-2025-33252] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.

[CVE-2025-33253] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution by convincing a user to load a maliciously crafted file. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.

[CVE-2025-60035] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] A vulnerability has been identified in the OPC.Testclient utility, which is included in Rexroth IndraWorks. All versions prior to 15V24 are affected. This flaw allows an attacker to execute arbitrary code on the user's system by parsing a manipulated file containing malicious serialized data. Exploitation requires user interaction, specifically opening a specially crafted file, which then causes the application to deserialize the malicious data, enabling Remote Code Execution (RCE). This can lead to a complete compromise of the system running the OPC.Testclient.

[CVE-2025-60036] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] A vulnerability has been identified in the UA.Testclient utility, which is included in Rexroth IndraWorks. All versions prior to 15V24 are affected. This flaw allows an attacker to execute arbitrary code on the user's system by parsing a manipulated file containing malicious serialized data. Exploitation requires user interaction, specifically opening a specially crafted file, which then causes the application to deserialize the malicious data, enabling Remote Code Execution (RCE). This can lead to a complete compromise of the system running the UA.Testclient.

[CVE-2025-60037] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] A vulnerability has been identified in Rexroth IndraWorks. This flaw allows an attacker to execute arbitrary code on the user's system by parsing a manipulated file containing malicious serialized data. Exploitation requires user interaction, specifically opening a specially crafted file, which then causes the application to deserialize the malicious data, enabling Remote Code Execution (RCE). This can lead to a complete compromise of the system running Rexroth IndraWorks.

[CVE-2025-60038] [Modified: 17-06-2026] [Analyzed] [V3.1 S7.8:HIGH] A vulnerability has been identified in Rexroth IndraWorks. This flaw allows an attacker to execute arbitrary code on the user's system by parsing a manipulated file containing malicious serialized data. Exploitation requires user interaction, specifically opening a specially crafted file, which then causes the application to deserialize the malicious data, enabling Remote Code Execution (RCE). This can lead to a complete compromise of the system running Rexroth IndraWorks.

[CVE-2026-1435] [Modified: 17-06-2026] [Analyzed] [V3.1 S9.8:CRITICAL] Not properly invalidated session vulnerability in Graylog Web Interface, version 2.2.3, due to incorrect management of session invalidation after new logins. The application generates a new 'sessionId' each time a user authenticates, but does not invalidate previously issued session identifiers, which remain valid even after multiple consecutive logins by the same user. As a result, a stolen or leaked 'sessionId' can continue to be used to authenticate valid requests. Exploiting this vulnerability would allow an attacker with access to the web service/API network (port 9000 or HTTP/S endpoint of the server) to reuse an old session token to gain unauthorized access to the application, interact with the API/web, and compromise the integrity of the affected account.

[CVE-2026-1436] [Modified: 17-06-2026] [Analyzed] [V3.1 S6.5:MEDIUM] Improper Access Control (IDOR) in the Graylog API, version 2.2.3, which occurs when modifying the user ID in the URL. An authenticated user can access other user's profiles without proper authorization checks. Exploiting this vulnerability allows valid users of the system to be listed and sensitive third-party information to be accessed, such as names, email addresses, internal identifiers, and last activity. The endpoint 'http://<IP>:12900/users/<my_user>' does not implement object-level authorization validations.

[CVE-2026-1437] [Modified: 17-06-2026] [Analyzed] [V3.1 S6.1:MEDIUM] Reflected Cross-Site Scripting (XSS) vulnerability in the Graylog Web Interface console, version 2.2.3, caused by a lack of proper sanitization and escaping in HTML output. Several endpoints include segments of the URL directly in the response without applying output encoding, allowing an attacker to inject and execute arbitrary JavaScript code when a user visits a specially crafted URL. Exploitation of this vulnerability may allow script execution in the victim's browser and limited manipulation of the affected user's session context, through the '/system/authentication/users/edit/' endpoint.

[CVE-2026-1438] [Modified: 17-06-2026] [Analyzed] [V3.1 S6.1:MEDIUM] Reflected Cross-Site Scripting (XSS) vulnerability in the Graylog Web Interface console, version 2.2.3, caused by a lack of proper sanitization and escaping in HTML output. Several endpoints include segments of the URL directly in the response without applying output encoding, allowing an attacker to inject and execute arbitrary JavaScript code when a user visits a specially crafted URL. Exploitation of this vulnerability may allow script execution in the victim's browser and limited manipulation of the affected user's session context, through the '/system/nodes/' endpoint.