News for hackers. Stuff that matters.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by fock on Friday November 20, 2026 @01:50AM (#50571033)
this bug was introduced by clankers most likely...
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by lionkor on Friday November 20, 2026 @02:12AM (#50571182)
likely based on what
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by fock on Friday November 20, 2026 @02:48AM (#50571447)
- version 4 got released this year - mid 2025 a lot of people appeared contributing out of nowhere - https://github.com/openssl/openssl/pull/29178 this rewrote the code for base64 - you can delve into it to check if this was human generated.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by mort96 on Friday November 20, 2026 @05:18AM (#50572645)
That contributor is definitely a vibe coder these days; just look at their profile's readme: https://github.com/Nick-Nuon, the only place I have ever seen that emoji list style where every bullet point starts with an emoji is from chat bots, but chat bots really really like it.

I don't see any obvious tells from the code diff though, I would've expected chatbot code to be more commented and nothing immediately stands out.

The commit messages and PR description don't read at AI-generated at all, there are small typos and grammatical issues. For example, the sentence "Originally, the OpenSSL base64 encoding kernel includes a buffer of ctx->length" confuses word tense a bit, correct grammar would've said "Originally, the OpenSSL base64 encoding kernel included ...". Chat bots are terrible at writing but typically impeccable when it comes to word tense and spelling.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by fock on Friday November 20, 2026 @06:01AM (#50572999)
Good to see that I'm not alone in seeing very weird things there - I also don't think it was vibecoded (back then, Claude wasn't there yet...) but they surely used an LLM (the passage you mentioned likely can easily be produced by pointing the LLM at 2 folders... - also scripts outputting emojis are a tell imo...).

I guess the PR back then was a bit of a CV-padding action, where they integrated their research into a widely used OSS-project. That the project maintainers just accepted this in good faith (tbh the PR is better than the last vibecoder I saw pushing into a rust-numerics projects: "enable AVX only on AMD because my broken 10 y.o. Intel clocks down when executing AVX...") bodes ill that our shared infrastructure survives this in usable "shape".