I tested my nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq5xamn8ghj7dnvv45xs7tywde8g6rpvakkjuekw46nvar4vdhxgan6wumkxatzwpckk6rk0puhjdm2da5k7ce5x4kkkumjx3jkzepwdahxjmmwqyt8wumn8ghj7un9d3shjtnwdaehgu3wd9hxvmckqw0xz node and it is not vulnerable. You may get different results with different services installed https://image.nostr.build/113cb03979d697434a35872646457c666a4f2eec9dc0466865f87ba989bf4503.jpg nostr:nevent1qqs0v27ejvkl5s7anap48wulk7mn2q2gt8l4a29pmhguacpxq5fcmuspz3mhxw309ucnydewxqhrqt338g6rsd3e9upzp6y2dy0f3kvc0jty2gwl7cqztas8qqmc5jrerqxuhw622qnc2pq3qvzqqqqqqy0ww6xs
If you have a linux device, install nmap if it isn't already installed then run this command to test your node and computers. sudo nmap -n -PN -sT -sU -p 631 $YOUR_NODE_IP_HERE nostr:nevent1qqsd0uejcglgyf6x3esjc2les60fszjp4auhj6k5e52gxj67hwsmy6spz3mhxw309ucnydewxqhrqt338g6rsd3e9upzqqgd7ry53l56k4xjedl2gg8l5zx409vfsxmw568g8248avka8uz6qvzqqqqqqy9emfkr
StartOS is not affected by this issue
Good to know it isn't even possible to have accidentally enabled CUPS on your start9 node. I wanted to test and share because I know when the "imminent disclosure" first made the rounds on nostr people were warning that it may affect nodes. It wasn't known that it was a CUPS issue at that time.