#cve20235129

Live, measured metrics for the hashtag #cve20235129 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 #cve20235129

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.

$10.85/ year · 11-character #name
Claim #cve20235129$10.85/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
6
Recent posts
Mastodon
~0.1/hr
Recent pace
Mastodon · last 6
0.8
Avg reactions / post
Mastodon · last 6
Reddit posts / month
Reddit search
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · mastodon.social (Mastodon public tags API) · fetched 2026-08-04 02:51 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 · mastodon.social (Mastodon public search API) · fetched 2026-08-04 02:51 UTC

No related tags with measured usage found for #cve20235129.

Live pulse

measured · mastodon.social (Mastodon tag timeline) · fetched 2026-08-04 02:51 UTC

Everything below is measured over the latest 6 public posts (spanning ~67 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (5) · French (1)

Avg boosts / post: 2.3

Top of the latest posts

  • @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]552023-09-26 13:39 UTCView post →
  • Hi @BillyJBryant Thank you very much for your explanation. Much appreciated. So yes based on your info and from what I have read so far this one can also be considered as a zero-click. What I did notice though is that #CVE20235129 has been

    Thijs Kromhout@[email protected]012023-09-29 06:59 UTCView post →
  • Good Morning, story so far on the next log4j level #vulnerability #CVE20234863 #CVE20235129 #0day #Chrome #iOS libwebp library is vulnerable to heap overflow and can lead to RCE. Apple assigned #CVE202341064 and #CVE202341061. Also actively

    d0pp3l6ang3r :verified: :donor:@[email protected]012023-09-28 01:50 UTCView post →

#cve20235129 across platforms

every network with a public tag surface

Follow #cve20235129 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/cve20235129