#servervulnerability
Live, measured metrics for the hashtag #servervulnerability from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #servervulnerability
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-07-27 14:44 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-07-27 14:44 UTCNo related tags with measured usage found for #servervulnerability.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 14:44 UTCEverything below is measured over the latest 2 public posts (spanning ~35941 hours).
Posting hours (UTC)
Languages: English (1) · French (1)
Avg boosts / post: 0.5
Top of the latest posts
HTTP/2 CONTINUATION Flood Vulnerability Analysis Date: April 3, 2024 CVE: N/A Vulnerability Type: CWE-400 (Resource Exhaustion) CWE: [[CWE-400]] Sources: nowotarski.info Issue Summary The CONTINUATION Flood vulnerability exploits a flaw in
#ActuLibre GhostCat: New High-Risk Vulnerability Affects Servers Running Apache Tomcat -> http://feedproxy.google.com/~r/TheHackersNews/~3/6hrVzZ1lzyw/ghostcat-new-high-risk-vulnerability.html #remotecodeexecution #remotefileinclusion #serv
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/servervulnerability