#cve_2023_5129

Live, measured metrics for the hashtag #cve_2023_5129 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #cve_2023_5129

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.

$5.00/ year · 13-character #name
Claim #cve_2023_5129 — $5.00/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
3
Recent posts
Mastodon
~0.1/hr
Recent pace
Mastodon · last 3
0.3
Avg reactions / post
Mastodon · last 3
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-08-04 01:33 UTC
0
07-29
0
07-30
0
07-31
0
08-01
0
08-02
0
08-03
0
08-04

0 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-04 01:33 UTC

No related tags with measured usage found for #cve_2023_5129.

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-04 01:33 UTC

Everything below is measured over the latest 3 public posts (spanning ~32 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (1)

Avg boosts / post: 9

Top of the latest posts

  • Okay, a continually-updated list of Electron apps and their Electron versions, and whether they're vulnerable to #CVE_2023_5129, aka #CVE_2023_4863. https://docs.google.com/spreadsheets/d/1QLLFYCO0FMAu1ob6mnYCapW8dnx-HXunbf_zc9QLXlM/edit?us

    Taggart :donor:@[email protected]♥ 1↻ 212023-09-27 21:06 UTCView post →

  • Wait what? Now it's not a valid CVE anymore? #CVE_2023_5129

    Taggart :donor:@[email protected]♥ 0↻ 12023-09-27 22:05 UTCView post →

  • @campuscodi This article claims that it is a new CVE for the same vulnerability, to clarify scope? https://stackdiary.com/heap-buffer-overflow-in-libwebp-cve-2023-5129/ But this seclists thread seems to say that CVE-2023-5129 is associated

    Royce Williams@[email protected]♥ 0↻ 52023-09-26 13:39 UTCView post →

#cve_2023_5129 across platforms

every network with a public tag surface

Follow #cve_2023_5129 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.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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/cve_2023_5129