Did you know SaaS now has its own CVE tag?

For years, vulnerabilities in SaaS services were hard to track – often without a CVE ID at all. That’s finally changing.

👉 The new exclusively-hosted-service tag tells you:

This issue affects only the hosted service (not on-prem).

In many cases, the provider has already fixed it – no customer patch needed.

Microsoft and Google are already using it. That means SaaS CVEs are now easier to find, easier to interpret, and easier to act on.

Why it matters:
Less noise. Better transparency. Smarter triage.

SaaS is the default – it’s about time our vulnerability management caught up. 🌥️🔐

#cybersecurity#SaaS#CVE

Dear @Gargron — Can we take another, fresh look at https://github.com/mastodon/mastodon/issues/20694 ? Hashtags should ultimately support full UTF8, IMHO, but adding at the very least the dash would be very helpful. It's not just band or artist names. CVEs are a better example. It would be really helpful when I can use #CVE-2025-6019 instead of #CVE20256019 as I am forced to do now. I guess hashtags are not in scope of the ActivityPub protocol, @evan ?

Added 𝗨𝗣𝗗𝗔𝗧𝗘 𝟭 - 𝗧𝗵𝗼𝘂𝗴𝗵𝘁𝘀 𝗔𝗳𝘁𝗲𝗿 𝗖𝗼𝗺𝗺𝗲𝗻𝘁𝘀 to the 𝗙𝗿𝗲𝗲𝗕𝗦𝗗 𝗝𝗮𝗶𝗹𝘀 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 article.

https://vermaden.wordpress.com/2025/04/11/freebsd-jails-security/

#containers#CVE #docker #freebsd #jail #jails #linux #podman #security #server #vnet #cve