320 Followers
185 Following
5.6K Posts

Little goblin with catears.

Unfinished projects, complaining about computers, reinventing the wheel (badly), has not fully read any docs since 2015.

Proud bot parent to four failsons:
@enojifier_bot
@dreizehnzwoelf_bot
@perfect10_bot
@dotdotslash_bot

Testimonials:
"not helpful" @LucasWerkmeister

All my opinions are that of my employer but they don't know it yet & I am not telling you were I work. Apropos: If you need some idiot to kick computers for purposes of making them secure hmu, this job fucking sucks (vulnerability management, automation/engineering for your soc/isrt, ...).

PFP by a lizard that I am pretty sure transitioned at some point but I kinda lost contact with around the same time so I might only know their deadname & at this point it's too awkward to seek them out & ask. So instead I am going to credit them by their last discord handle I am aware of: fuck, md

LanguagesGerman, English
Pronomen (πŸ‡©πŸ‡ͺ)egal
Pronouns (πŸ‡¬πŸ‡§/πŸ‡ΊπŸ‡Έ)name reference > they/it > whatever
@chillybot furiously hitting boost button I love those!!! @grey
Yeehaw pardner #moopsy #StarTrek
@phillip rm -rf --no-preserve-root / 
Booo! Booooooo! In the *.infosec.exchange family, even!!! 
@JadedBlueEyes also no. A notification once they stop breathing would be nice though 😌 ,

@JadedBlueEyes sigh I'd be fine with it if it was just one big dump. Unfortunately the CVE publications or Metrics additions seem to be kinda piecemeal so it's, like, 4 or 5 Totolink posts now?

But, I mean, I have been thinking about "days since $severity vuln in $vendor" bot... πŸ€”

@perfect10_bot ok, I am pulling the trigger on the cvss2 thing already...

Edit: Implemented now. Poll will still be running so if you want it back I we can do that, too 

@FritzAdalis @hrbrmstr listed as Not Exploited, so unlikely
I wish I could communicate with insects. i am absolutely willing to share parts of my appartment & my food with them, but there are some pretty clear boundaries & I just wanna tell the lil fellas so I dont have to throw them out entirely 

During the last three months, from 25 February to 25 May 2026, GCVE has continued moving beyond an identifier-allocation concept into a practical ecosystem for publishing, correlating, enriching and consuming vulnerability information.

What have we accomplished over the past three months? Quite a lot. To learn more about our latest public developments and ongoing work, read our latest status update on the blog:

πŸ”— https://gcve.eu/2026/05/25/gcve-recent-activities-building-a-decentralised-and-operational-vulnerability-ecosystem/

#cve #gcve #vulnerabilitymanagement #cybersecurity

GCVE recent activities: building a decentralised and operational vulnerability ecosystem

A review of GCVE activities and achievements from 25 February to 25 May 2026, including new and revised Best Current Practices, based on public GitHub work and official GCVE publications.