Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
nublado

14 ℃

94%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 20:30:01

[USD] USD 75,665.63

[BRL] BRL 381,377.46 [USD] USD 75,665.63 [GBP] GBP 56,294.62 [EUR] EUR 65,181.25
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 - 20:53:43 up 245 days, 5:25, 3 users, load average: 0.00, 0.00, 0.00

[22/05/2026 18:27] Justiça italiana anula aval para extradição de Zambelli, que já foi liberada da prisão, diz defesa - O Globo

[22/05/2026 15:50] Datafolha: Lula abre 9 pontos na liderança do 1º turno após escândalo Vorcaro-Dark Horse - CartaCapital

[22/05/2026 12:57] Mendonça autoriza volta de Vorcaro para cela especial na PF - Poder360

[22/05/2026 16:34] Veja como é por dentro o presídio para onde Deolane Bezerra foi levada - Notícias da TV

[22/05/2026 18:48] Ex-funcionária pagou cartão da esposa de Mario Frias e fez PIX para ex-chefe de gabinete, indicam comprovantes bancários - G1

[22/05/2026 03:55] Fim da escala 6x1 esbarra em falta de auditores fiscais, alerta relator - Correio Braziliense

[22/05/2026 17:37] Prefeito anuncia pagamento por Pix, cartões de débito e crédito nos ônibus do Rio antes do fim do dinheiro nas passagens - O Globo

[22/05/2026 15:46] Previsão Fim de Semana (23 e 24/05): Chuva forte e alerta para temporais em áreas do estado de SP - Climatempo

[22/05/2026 15:44] Ciclone intensifica ‘chuvarada’, risco de geadas e nova friagem na Amazônia no fim de semana - ND Mais

[22/05/2026 16:15] Polícia encontra "fazenda de mineração" do CV em comunidade no Rio; entenda - CNN Brasil

[CVE-2026-22281] [Modified: 28-01-2026] [Analyzed] [V3.1 S3.5:LOW] Dell PowerScale OneFS, versions 9.5.0.0 through 9.5.1.5, versions 9.6.0.0 through 9.7.1.10, versions 9.8.0.0 through 9.10.1.3, versions starting from 9.11.0.0 and prior to 9.13.0.0, contains a Time-of-check Time-of-use (TOCTOU) race condition vulnerability. A low privileged attacker with adjacent network access could potentially exploit this vulnerability, leading to denial of service.

[CVE-2025-9289] [Modified: 16-03-2026] [Analyzed] [V3.1 S4.7:MEDIUM] A Cross-Site Scripting (XSS) vulnerability was identified in a parameter in Omada Controllers due to improper input sanitization. Exploitation requires advanced conditions, such as network positioning or emulating a trusted entity, and user interaction by an authenticated administrator. If successful, an attacker could execute arbitrary JavaScript in the administrator’s browser, potentially exposing sensitive information and compromising confidentiality.

[CVE-2026-0798] [Modified: 29-01-2026] [Analyzed] [V3.1 S3.5:LOW] Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing release titles, tags, and content.

[CVE-2026-20736] [Modified: 29-01-2026] [Analyzed] [V3.1 S7.5:HIGH] Gitea does not properly verify repository context when deleting attachments. A user who previously uploaded an attachment to a repository may be able to delete it after losing access to that repository by making the request through a different repository they can access.

[CVE-2026-20750] [Modified: 29-01-2026] [Analyzed] [V3.1 S9.1:CRITICAL] Gitea does not properly validate project ownership in organization project operations. A user with project write access in one organization may be able to modify projects belonging to a different organization.

[CVE-2026-20800] [Modified: 29-01-2026] [Analyzed] [V3.1 S6.5:MEDIUM] Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.

[CVE-2026-20883] [Modified: 29-01-2026] [Analyzed] [V3.1 S6.5:MEDIUM] Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.

[CVE-2026-20888] [Modified: 29-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface. A user with read access to pull requests may be able to cancel auto-merges scheduled by other users.

[CVE-2026-20897] [Modified: 29-01-2026] [Analyzed] [V3.1 S9.1:CRITICAL] Gitea does not properly validate repository ownership when deleting Git LFS locks. A user with write access to one repository may be able to delete LFS locks belonging to other repositories.

[CVE-2026-20904] [Modified: 29-01-2026] [Analyzed] [V3.1 S6.5:MEDIUM] Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings of other users' OpenID identities.

[CVE-2026-20912] [Modified: 29-01-2026] [Analyzed] [V3.1 S9.1:CRITICAL] Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users.

[CVE-2026-23831] [Modified: 02-02-2026] [Analyzed] [V3.1 S5.3:MEDIUM] Rekor is a software supply chain transparency log. In versions 1.4.3 and below, the entry implementation can panic on attacker-controlled input when canonicalizing a proposed entry with an empty spec.message, causing nil Pointer Dereference. Function validate() returns nil (success) when message is empty, leaving sign1Msg uninitialized, and Canonicalize() later dereferences v.sign1Msg.Payload. A malformed proposed entry of the cose/v0.0.1 type can cause a panic on a thread within the Rekor process. The thread is recovered so the client receives a 500 error message and service still continues, so the availability impact of this is minimal. This issue has been fixed in version 1.5.0.

[CVE-2026-23953] [Modified: 30-01-2026] [Analyzed] [V3.1 S8.7:HIGH] Incus is a system container and virtual machine manager. In versions 6.20.0 and below, a user with the ability to launch a container with a custom YAML configuration (e.g a member of the ‘incus’ group) can create an environment variable containing newlines, which can be used to add additional configuration items in the container’s lxc.conf due to newline injection. This can allow adding arbitrary lifecycle hooks, ultimately resulting in arbitrary command execution on the host. Exploiting this issue on IncusOS requires a slight modification of the payload to change to a different writable directory for the validation step (e.g /tmp). This can be confirmed with a second container with /tmp mounted from the host (A privileged action for validation only). A fix is planned for versions 6.0.6 and 6.21.0, but they have not been released at the time of publication.

[CVE-2026-23954] [Modified: 30-01-2026] [Analyzed] [V3.1 S8.7:HIGH] Incus is a system container and virtual machine manager. Versions 6.21.0 and below allow a user with the ability to launch a container with a custom image (e.g a member of the ‘incus’ group) to use directory traversal or symbolic links in the templating functionality to achieve host arbitrary file read, and host arbitrary file write. This ultimately results in arbitrary command execution on the host. When using an image with a metadata.yaml containing templates, both the source and target paths are not checked for symbolic links or directory traversal. This can also be exploited in IncusOS. A fix is planned for versions 6.0.6 and 6.21.0, but they have not been released at the time of publication.

[CVE-2026-23988] [Modified: 27-02-2026] [Analyzed] [V3.1 S7.3:HIGH] Rufus is a utility that helps format and create bootable USB flash drives. Versions 4.11 and below contain a race condition (TOCTOU) in src/net.c during the creation, validation, and execution of the Fido PowerShell script. Since Rufus runs with elevated privileges (Administrator) but writes the script to the %TEMP% directory (writeable by standard users) without locking the file, a local attacker can replace the legitimate script with a malicious one between the file write operation and the execution step. This allows arbitrary code execution with Administrator privileges. This issue has been fixed in version 4.12_BETA.

[CVE-2026-24058] [Modified: 18-02-2026] [Analyzed] [V3.1 S9.8:CRITICAL] Soft Serve is a self-hostable Git server for the command line. Versions 0.11.2 and below have a critical authentication bypass vulnerability that allows an attacker to impersonate any user (including admin) by "offering" the victim's public key during the SSH handshake before authenticating with their own valid key. This occurs because the user identity is stored in the session context during the "offer" phase and is not cleared if that specific authentication attempt fails. This issue has been fixed in version 0.11.3.

[CVE-2026-24117] [Modified: 02-02-2026] [Analyzed] [V3.1 S5.3:MEDIUM] Rekor is a software supply chain transparency log. In versions 1.4.3 and below, attackers can trigger SSRF to arbitrary internal services because /api/v1/index/retrieve supports retrieving a public key via user-provided URL. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. The issue has been fixed in version 1.5.0. To workaround this issue, disable the search endpoint with --enable_retrieve_api=false.

[CVE-2025-53968] [Modified: 02-02-2026] [Analyzed] [V3.1 S7.5:HIGH] This vulnerability arises because there are no limitations on the number of authentication attempts a user can make. An attacker can exploit this weakness by continuously sending authentication requests, leading to a denial-of-service (DoS) condition. This can overwhelm the authentication system, rendering it unavailable to legitimate users and potentially causing service disruption. This can also allow attackers to conduct brute-force attacks to gain unauthorized access.

[CVE-2025-54816] [Modified: 02-02-2026] [Analyzed] [V3.1 S9.4:CRITICAL] This vulnerability occurs when a WebSocket endpoint does not enforce proper authentication mechanisms, allowing unauthorized users to establish connections. As a result, attackers can exploit this weakness to gain unauthorized access to sensitive data or perform unauthorized actions. Given that no authentication is required, this can lead to privilege escalation and potentially compromise the security of the entire system.

[CVE-2025-55705] [Modified: 12-02-2026] [Analyzed] [V3.1 S7.3:HIGH] This vulnerability occurs when the system permits multiple simultaneous connections to the backend using the same charging station ID. This can result in unauthorized access, data inconsistency, or potential manipulation of charging sessions. The lack of proper session management and expiration control allows attackers to exploit this weakness by reusing valid charging station IDs to establish multiple sessions concurrently.