node/security-relevant fixes

F-TON-009-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

ton-blockchain/tonReported fixton-blockchain/ton

node/security-relevant fixes

fixed publicly (mapped by date and fix area)

details

Finding IDs: F-TON-009-001
Status: fixed publicly (mapped by date and fix area)
Reported via: TON contest / security process
Note: PR #2208 merged on 2026-03-17 with merge commit 3abee30359120c51bfbbd05a589ae31ffa7d453d. the public PR includes node/security-relevant fixes including error handling and memory allocation fixes; the merge commit remains present in current testnet and master.

F-TON-009-001: Needs source detail. A multi-fix change is mapped by date/area, without enough public detail for this exact report. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TON-009-001

Security area (1seal assessment): Unclassified. The linked PR contains several node and database fixes; no exact public finding-to-change mapping identifies a primary security area. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.