nyan (npub1t9q…r0p6)
CVE references, in my experience, go bad way way faster than Wikipedia links. A lot of the time it's a proof of concept script that gets put up somewhere just long enough to get added as a reference before taken down (either willingly or unwillingly), but I have also seen vendor advisories that are dead links due to never setting up redirects when they update their links, or the company gets acquired and deletes all their old KB articles, or the company decides that advisories should be behind a customer portal. Things like that. As da_667 said, especially for iot vulns you can see a proof of concept script put on GitHub or notion at 9 am in a Monday, bookmark it, and then the link is dead by Wednesday.
On top of that, you sometimes see reference links that get lost in translation somehow. I saw an exploit on exploitdb the other day for titools printmonitor. The script accurately showed the titools . eu url for the vendor. The nuclei template somehow turned it into ti-tools . com and then print . com for some reason.
Documentation doesn't directly make money for vendors, so it doesn't get the same level of care as other things. That makes some sense until your CTI platform is highly reliant on now-dead links.
Dio9sys
npub1n4…sjm05
2026-08-23 19:07:00 UTC
in reply to nevent1q…4glq
Author Public Key
npub1n4ktayy64wsep787y8ffnch0qqtyyp2zcx660rjrwfjc7dvp8c0s4sjm05Seen on
wss://relay.momostr.pinkPublished at
2026-08-23 19:07:00 UTCEvent JSON
{
"id": "81ea09cdc9c8120947ec7a2b284098c32d388465fff14e1feadfb1212ee15c45",
"pubkey": "9d6cbe909aaba190f8fe21d299e2ef0016420542c1b5a78e4372658f35813e1f",
"created_at": 1787512020,
"kind": 1,
"tags": [
[
"e",
"c624fdeff26d117c86a39f26adc671674480ca2f7346e2883e1143b23fd99762",
"",
"root",
"5941667d19e40b7581976ddf20bfae28022f6837f5467c96f0e377da7ba264a2"
],
[
"p",
"87b08bf48dd639cf2e6c33b46f98146b44f40e05a696274012a159463398437d"
],
[
"p",
"5941667d19e40b7581976ddf20bfae28022f6837f5467c96f0e377da7ba264a2"
],
[
"e",
"b2f230bb9c25fa3fadffbf10ad3a5f8a4db1a74ffbe726ad45750b413ea6cd59",
"",
"reply",
"87b08bf48dd639cf2e6c33b46f98146b44f40e05a696274012a159463398437d"
],
[
"proxy",
"https://haunted.computer/@Dio9sys/117146387766305013",
"web"
],
[
"p",
"9d6cbe909aaba190f8fe21d299e2ef0016420542c1b5a78e4372658f35813e1f"
],
[
"proxy",
"https://haunted.computer/users/Dio9sys/statuses/117146387766305013",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://haunted.computer/users/Dio9sys/statuses/117146387766305013",
"pink.momostr"
],
[
"-"
]
],
"content": "nostr:npub1t9qkvlgeus9htqvhdh0jp0aw9qpz76ph74r8e9hsudma57azvj3qndr0p6\n\nCVE references, in my experience, go bad way way faster than Wikipedia links. A lot of the time it's a proof of concept script that gets put up somewhere just long enough to get added as a reference before taken down (either willingly or unwillingly), but I have also seen vendor advisories that are dead links due to never setting up redirects when they update their links, or the company gets acquired and deletes all their old KB articles, or the company decides that advisories should be behind a customer portal. Things like that. As da_667 said, especially for iot vulns you can see a proof of concept script put on GitHub or notion at 9 am in a Monday, bookmark it, and then the link is dead by Wednesday.\n\nOn top of that, you sometimes see reference links that get lost in translation somehow. I saw an exploit on exploitdb the other day for titools printmonitor. The script accurately showed the titools . eu url for the vendor. The nuclei template somehow turned it into ti-tools . com and then print . com for some reason.\n\nDocumentation doesn't directly make money for vendors, so it doesn't get the same level of care as other things. That makes some sense until your CTI platform is highly reliant on now-dead links.",
"sig": "4de4f5475b0accf5d54525ed551233a298944c810c7a31a423bd6cfd7df80b1ee0965a11e0d8fa45792ec0b84d648747febdf8009358ce272c6f2c830409615c"
}