#核心漏洞
Live, measured metrics for the hashtag #核心漏洞 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #核心漏洞
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-08-25 01:25 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-08-25 01:25 UTCNo related tags with measured usage found for #核心漏洞.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-25 01:25 UTCEverything below is measured over the latest 4 public posts (spanning ~2937 hours).
Posting hours (UTC)
Languages: Chinese (Taiwan) (4)
Avg boosts / post: 0
Top of the latest posts
🌗 核心健全性漏洞 #14576 事後剖析 — 萊昂納多·德·莫拉 ➤ 從漏洞修復到主動防禦:Lean 如何利用 AI 與獨立驗證加固數學證明防線 ✤ https://leodemoura.github.io/blog/2026-8-1-postmortem-for-kernel-soundness-bug-14576/ 本文為 Lean 語言創辦人 Leonardo de Moura 針對 Lean 核心健全性漏洞(#14576)所撰寫的事後剖析。該漏洞源於 Lean 核
🌘 赦免 MIE?——深入剖析蘋果 M5 晶片的記憶體防護被繞過事件 ➤ 當「世代級」安全防護遇上簡單的整數溢位 ✤ https://ironpeak.be/blog/bypassing-apple-mie/ 蘋果斥資多年開發的「記憶體完整性強制執行」(MIE)技術,號稱是消費級系統中最嚴密的記憶體防護網,旨在透過硬體標記與唯讀區域監控來根絕核心層級的記憶體漏洞。然而,由 Calif.io 團隊協同 AI 工具,僅耗時五天便成功攻破此防線。本文揭露了該漏洞的根源——在負責修
🌗 FreeBSD 安全公告:針對 execve() 系統呼叫的本地權限提升漏洞 (FreeBSD-SA-26:13.exec) ➤ 核心邏輯漏洞恐致系統淪陷, FreeBSD 強制建議立即修補 ✤ https://www.freebsd.org/security/advisories/FreeBSD-SA-26:13.exec.asc FreeBSD 專案近期發佈了針對系統核心的重大安全更新,修正了一項存在於 `execve(2)` 系統呼叫中的本地權限提升漏洞。該漏洞源
#核心漏洞 across platforms
every network with a public tag surfaceFollow #核心漏洞 straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/核心漏洞