Skip to content

Conversation

@todb
Copy link
Contributor

@todb todb commented Aug 15, 2025

CVE-2025-8452, the CVE ID, is already published, so we should publish our own advisory for it.

Also, since we're a GCNA, we should start using that, too.

We've decided to be extra silly with our GCVE IDs. Don't ruin the surprise! (See the private discord for details on what this long ass binary string means.)

@todb
Copy link
Contributor Author

todb commented Aug 15, 2025

As a bonus, you can now navigate to GCVEs directly (once this lands):

https://takeonme.org/gcves/GCVE-1337-2025-00000000000000000000000000000000000000000000000001011111011111010111111001000000000000000000000000000000000000000000000000000000001

will totally work.

Here's the render locally:

intentional overflow of the table for the GCVE ID that's stupidly long

@todb todb requested a review from mauvehed August 15, 2025 00:12
todb added 2 commits August 14, 2025 19:13
Signed-off-by: Tod Beardsley <[email protected]>
Signed-off-by: Tod Beardsley <[email protected]>
@todb
Copy link
Contributor Author

todb commented Aug 15, 2025

And I'm here's the screenshot rendered:

Yo dog, I heard you liked screenshots, so here's a screenshot of a screenshot.

Signed-off-by: Tod Beardsley <[email protected]>
@todb todb merged commit 5fe0601 into AustinHackers:main Aug 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant