11 ms·
Anonymous GitHub account mass-dropping undisclosed 0-days
- functionmouse 4mo agowe have got to stop putting our bank accounts and SSNs on computers
- gnerd00 4mo ago... support cash, tell your neighbors
- JohnMakin 4mo agotil you get debanked
- krapp 4mo agoCash doesn't require a bank.
- speedgoose 4mo agoBanks are kinda useful to avoid getting robbed all your money, on a regular basis. Many French people with crypto money experienced that the hard way recently.
- nubg 4mo agodo you have links about the french people?
- speedgoose 4mo agoSure, here are a few links. Use your favourite translator. In short, it's a very active and growing activity. Many data leaks helped people to identify wealthy targets. Some just brag about having crypto. https://www.lemonde.fr/societe/article/2026/04/24/enlevements-dans-le-secteur-des-cryptomonnaies-88-mises-en-examen-dans-les-enquetes-en-cours-selon-le-pnaco_6683108_3224.html https://www.lemonde.fr/societe/article/2026/04/24/enlevement... https://www.franceinfo.fr/faits-divers/cryptomonnaies-la-vague-d-enlevements-contre-le-secteur-ne-ralentit-pas-alerte-un-expert-en-securite-qui-pointe-des-prestataires-defaillants_7790333.html https://www.franceinfo.fr/faits-divers/cryptomonnaies-la-vag... https://www.lemonde.fr/societe/article/2025/08/19/l-ascension-et-la-chute-d-un-gang-de-kidnappeurs-specialise-dans-les-rancons-en-cryptomonnaie-une-fois-un-doigt-coupe-on-enchaine-toutes-les-heures_6631788_3224.html https://www.lemonde.fr/societe/article/2025/08/19/l-ascensio... (paywall) https://www.slate.fr/societe/enlevements-lies-cryptomonnaies-moyen-sur-gagner-argent-kidnapping-sequestration-extorsion-torture-crime-organise-france-cryptorapts https://www.slate.fr/societe/enlevements-lies-cryptomonnaies... Some random recent ones we know about: https://france3-regions.franceinfo.fr/grand-est/haut-rhin/mulhouse/un-homme-enleve-sequestre-et-vole-apres-avoir-parle-de-ses-investissements-dans-la-cryptomonnaie-quatre-personnes-interpellees-3363202.html https://france3-regions.franceinfo.fr/grand-est/haut-rhin/mu... https://www.leparisien.fr/faits-divers/renseignes-par-des-hackers-les-faux-policiers-agressent-un-pere-de-famille-pour-son-epargne-en-cryptomonnaies-14-06-2026-NQWFM4NDONBPLGAAJL3MQH63OI.php https://www.leparisien.fr/faits-divers/renseignes-par-des-ha...
- ahoka 4mo agoKinda does?
- krapp 4mo agoDoesn't at all. You can take cash, keep cash and spend cash without any bank being involved. Cash is more anonymous than crypto and (if it's USD) accepted just about everywhere. Banks give you an advantage with transaction security and deposit insurance, but that's dealing with money and not cash.
- ahoka 4mo agoI understand that it is different in the US, but most countries’ cash is printed by some kind of central bank.
- Cider9986 4mo agoAnd Monero for online.
- ryandrake 4mo agoWe need our infrastructure to stop treating bank account numbers and social security numbers as secrets. At least in the US, bank account numbers appear on physical checks and are required to be shared in order to do an ACH transfer, and a social security number is not supposed to be used as an identifier (unless to the Social Security Administration itself) or as a secret password. Ideally, nothing nefarious should happen if both of them were listed and queryable publicly.
- derektank 4mo agoIt’s quite ridiculous that we haven’t been able to build a modern identification system capable of replacing SSNs in the last 30 years.
- timacles 4mo agoSSNv6. It will take 20 years for a 50% migration
- silversmith 4mo agoHang on, can you actually do something nefarious with just the bank account number?
- mystifyingpoi 4mo agoAFAIK that's US thing. In normal countries bank account numbers are not a secret. The worst thing that can happen is someone sending you money.
- ryandrake 4mo agoIf someone has your bank account and bank’s routing number (which is also not secret), they can make fraudulent ACH transfers and payments from your account. Of course it will most likely be caught as fraud some time after the fact, but just those two bits of not-secret info are enough to grief someone.
- 4mo ago
- pixel_popping 4mo agoFirewalled VM, locked-in keyboard/mouse, 1 query to any agent and it's setup.
- dgellow 4mo agoYou all need a better system than US SSNs
- DANmode 4mo agoYou can buy your SSN for $6-$10.
- smsm42 4mo agoYour SSN had been already stolen in the Equifax breach - unless you're so young or recently arrived that you haven't had SSN by then, in which case it had been stolen in one of a dozens of the breaches since then. And if somehow you avoided all that, it will be stolen in the inevitable next breach, which would happen regardless of what you do.
- merelydev 4mo agoMost of the exploits are for opensource/free software. I don't know what methods where used to find these exploits but I am starting to think security through obscurity might not be a bad thing in this day and age, where someone can just let bots loose on your codebase.
- serf 4mo agollms are fantastic disassembly partners, they're quite good at labeling functions from various dissassemblers -- the net losses from losing the benefits of open source , imo , outweigh the protection afforded by hiding your source code in yet another layer that is more and more easily unrolled through automated procedures.
- spongebobstoes 4mo agodisassembly only applies to client side software something like nginx could arguably be more secure if it was closed source (I am a proponent of and contributor to open source)
- gpm 4mo agoOnly until a single server running nginx is hacked and the binary leaked though...
- Hizonner 4mo agoUm, the nginx binary would have to be in the hands of hundreds of thousands of server operators. And the set of server operators is rich in the kind of person who would attack it. Not to mention the huge number of leaks you'd get. Maybe if it's some server-side software that you only use yourself...
- deleted 4mo ago[deleted]
- blensor 4mo agoAnd isn't it also mostly a transitioning issue. Those open codebases will be constantly scanned for potential security issues and getting more and more hardened. There are probably a lot of easy wins that are going to be discovered over the next few years but it should taper out after a while.
- Tiberium 4mo agoAre they all actually 0-day? I think a lot of them are from disclosed CVEs/code that were already fixed upstream. It often seems like the term "0-day" has lost most of its meaning today and people often use it to refer to any exploits.
- tempest_ 4mo agoRepo claims > A single archive of public exploit PoCs and vulnerability research writeups. At the time I post these, none have been reported. Feel free to report them yourself and take credit for the CVE if handed out lulz. Please do not abuse these. I do this so to allure people into the field, and I've always found this is the most efficient way. Which is roughly the definition of zero day. Whether the contents of the repo reflect the above claim is something else entirely.
- tyre 4mo ago> Please do not abuse these. Reminds me of Jamie Wolf's joke about bestiality laws. Who are those for? What stops most people from bestiality is… not wanting to have sex with animals! For people who do want to, what, they won't because of… the law?? Who will this comment stop??
- utopiah 4mo agoIf it stops even just 1 person once, isn't it already worth it?
- Valodim 4mo agoWe slaughter animals millions by the day in an industrialized fashion. I'm sure they'll feel much better that even singular instances of sexual harassment are officially not ok on paper.
- jodrellblank 4mo ago“Millions a day” is quite a low estimate; “””here are the best estimates of how many animals are killed every day on a per-species basis. Chickens: 206 million/day Farmed Fish: Between 211 million and 339 million Wild Fish: Between 3 billion and 6 billion Ducks: 9 million Pigs: 4 million Geese: 2 million Sheep: 1.7 million Rabbits: 1.5 million Turkeys: 1.4 million Goats: 1.4 million Cows: 846,000 Pigeons & other birds: 134,000 Buffalo: 77,000 Horses: 13,000 Other animals: 13,000 In total, this means that every 24 hours, between 3.4 and 6.5 billion animals are killed for food””” - https://sentientmedia.org/how-many-animals-are-killed-for-food-every-day/ https://sentientmedia.org/how-many-animals-are-killed-for-fo...
- jdw64 4mo agoI'm going through each one, and it's fascinating to see things like this. The UAF principle in c-ares is really interesting. The problem ultimately came from not being able to prevent stale pointers. The attack works by figuring out the size of the stale pointer, then spraying memory with data of the same size, and finally achieving RCE (Remote Code Execution). How do people even come up with ideas like this?
- jdw64 4mo agoBut do people actually find these vulnerabilities on their own, or are they using LLMs? I was curious about how these vulnerabilities work, so I tried asking my dear friend Mr. CLAUDE, but he immediately threw an error and ended the session because it was a cybersecurity question. Enterprise APIs block even the analysis itself, so it's amazing that people can actually pull this off in practice.
- lacoolj 4mo agoI imagine this is a large open model like GLM5.2 etc
- raesene9 4mo agoIf you want to chat with Claude about this, I'd recommend using Opus 4.6. IME it's happy to talk about (and even write) PoC exploits
- nicce 4mo agoPeople have always used tools. Some people have better tools than others. I guess the line is thin whether they found on their own or not.
- ZappoMan 4mo ago[flagged]
- jeffbee 4mo agole sigh, c-ares. Very predictable outcome. If you ever find yourself entertaining the idea that you will simply write non-blocking network protocol stacks in C with manual lifetime management, slap yourself. It doesn't matter if you think you are a super genius of unimpeachable taste. The job is impossible.
- mrbluecoat 4mo agoA surprising amount of documentation if the actor was just LLM-dropping these..
- Retr0id 4mo agoWhy is that surprising? LLMs can churn out arbitrary volumes of "documentation" in an instant.
- Bengalilol 4mo agoThis was sarcasm, meaning exactly what you wrote.
- Retr0id 4mo agoI can't see how it could possibly be read as sarcasm.
- Bengalilol 3mo agoLitotes maybe?
- dawnerd 4mo agoThat seems trivial for an llm to provide.
- tliltocatl 4mo agoA friendly reminder that a 0-day is a vulnerability that wasn't known until after a malicious actor exploited it. If someone publishes a PoC, it is not a 0-day, just a vulnerability.
- Retr0id 4mo agoNo, the days start counting from the availability of a patch.
- rmast 4mo agoI was thinking that the other definition was right and this correction was wrong. Then I did some searching and found multiple examples of both definitions in use, making things murky. So I turned to Merriam-Webster’s dictionary: “ of, relating to, or being a vulnerability (as in a computer or computer system) that is discovered and exploited (as by cybercriminals) before it is known to or addressed by the maker or vendor” And of course they use an “or” to make it ambiguous as to whether the days start counting when the vulnerability becomes known, or when the vendor has addressed it.
- 0123456789ABCDE 4mo agowhat if a path is never released?
- richbell 4mo agoI've only heard it used as Retr0id's definition.
- cubefox 4mo ago> A friendly reminder that a 0-day is a vulnerability that wasn't known until after a malicious actor exploited it. No, the full name was always "zero-day exploit". The number 0 refers to the days between the vulnerability being known by the vendor and the public availability of the exploit. So the vendor has zero days to create a security patch before the release of the exploit. The term "zero-day vulnerability" is a derived term to refer to a vulnerability affected by a zero-day exploit. Similarly, a "zero-day attack" is a derived term to refer to an attack carried out using a zero-day exploit.
- Retr0id 4mo agoI took a look at the Ghidra ones (because I use Ghidra), and I'm unimpressed: https://github.com/bikini/exploitarium/blob/main/ghidra-12.1.2-rce-ace-calc-poc/docs/classification.md https://github.com/bikini/exploitarium/blob/main/ghidra-12.1... The first requires being able to overwrite binaries in the Swift tool directory. Yes, if you overwrite binaries executed by ghidra, you can trigger code execution. This is not a surprise. The second, idk, I'm not familiar with TraceRMI (but it's probably worth noting that "RMI" stands for Remote Method Invocation). The third is not a vulnerability in the slightest, they just demonstrate that native 7zip parsing code is reachable. Maybe there is a bug in the 7zip parser, but without that it's meaningless.
- skerit 4mo agoI immediately saw the Ghidra one and was thinking: huh?
- firefax 4mo agoThe bigger takeaway is someone that smart is pissed off and dropping their shit with zero warning... but hey, that's just like, my opinion man.
- Retr0id 4mo agoYou don't need to be pissed off to decide that immediate public disclosure is the best option.
- ohadkr 4mo ago[flagged]
- kodareef5 4mo agotrying something new? this is interesting. the problem is that submitting reports is too slow. if you find one then your not supposed to share. but then over the next 90 days you learn no one cares and 13 other people submitted it before you, 43 after. maybe better that we just know. so we can run code we can trust sooner. zero is the proper number of dependencies. otherwise assume its broken.
- drob518 4mo agoThere is going to be a flurry of this sort of stuff as the AIs get smart enough to find them. It will naturally die down as the legitimate ones are fixed. Yes, there will always be some level of this, but I’d expect it to be low and the exploits found to be increasingly complex. This is a time of transition.
- jMyles 4mo ago> It will naturally die down as the legitimate ones are fixed. Seems like we're already in the middle of this phase, but rather than dying down, the 'reports' have just gotten more noisy and obtuse, making it more difficult to establish the actual degree of threat / attack vector.
- justacrow 4mo agoAnd if you are a state agency who'd like to keep the undisclosed zero-days you rely on secret, spamming maintainers with reports makes sense. As a bonus if you find any actual zero-days in your mass-generated ones you don't report it and get a new one to play with.
- alwa 4mo agoI mean. Makes sense until adversary states start walking through the same doors you’re using. At which point you might regret that maintainers are too flooded to deal with it. Assuming, of course, said state agency is operating under sufficiently strategic governance and management…
- utopiah 4mo ago> a flurry of this sort of stuff as the AIs get smart enough to find them. I really think this characterization is misleading. It's not "getting smart", only more tailored toward a specific usage, better curated dataset, better harness, better prompts, better labeling of results, documentation of failures and success, etc. The outcome is (hopefully) overall better but this anthropomorphized wording makes it sound like AI itself is somehow changing or evolving. No, both academia doing fundamental research, industry making it available commercially, and finally security researchers making the entire tooling and process packaged as a service are actively shaping it to make it better. There is no "it".
- johnwheeler 4mo agoThat's one way to do it.
- segmondy 4mo agoWhat if this person is from an AI lab that really wants the govt to keep suppressing Mythos/Fable & GPT5.6? It's what I would do, the timing couldn't be any better.
- 0123456789ABCDE 4mo agowouldn't it be trivial to match the repo to the user logs?
- segmondy 4mo agomy point is that if someone is releasing these without access to mythos/gpt5.6, then it can spook to govt and cause them to keep suppressing access to those models. if i'm competing with anthropic or openai and feel they have pulled far ahead, this is a decent move. i didn't say that it is for sure what's going on, but hey, there's a tiny bit of probability that it can't be ruled out.
- doe88 4mo ago0-days-vibes-vulns? There should be a new category, for spotting and handling the em-dashes of this brave new world of vulns and making the old fossils like me only picking my head up for the old painfully still hand-crafted artisanal ones instead. A kind of label, like free-range for eggs, in sum.
- tyre 4mo agoYes, big pet peeve of the new world. Every em dash is apparently an AI trigger. Back in my day, they were a sign of great respect within my people.
- Barbing 4mo agoI might like to see a collection of pre-2022 em-dash usage—a subset I suppose of the Low Background Steel category (https://lowbackgroundsteel.ai https://lowbackgroundsteel.ai).
- sureMan6 4mo agoYou completely misunderstanding the comment feels like an AI trigger
- rogerrogerr 4mo agoI used to be an em-dash user, but now my opinion is that I’d rather be perceived as someone who does not want to be confused with an LLM. So I’ve changed my writing style.
- jackp96 4mo agoThey're just so handy! I do think LLMs tend to use them in a specific way, though. So maybe tweaking your usage (ex. no spaces around them) or using a technically incorrect en-dash might offer the desired effect while subtly signaling that your message isn't AI-generated. I still use them — mostly for pauses — but I'd like to think my voice sounds distinct enough from an AI that people can tell.
- 4mo ago
- haberdasher 4mo ago"cybercrime is cringe"
- jmward01 4mo agoI think people may miss the point of a repo like this. Individually these are small puzzle pieces that can't do anything. Put them all in one place and it becomes easier to pick up pieces and try them together to see if they fit and build something bigger. Get enough pieces to fit together and you actually have something. This is the 'FOUO' idea in security. Enough open information gathered together in one place crosses the boundary from 'just public info' to 'secret stuff here!'. Now we have automatic puzzle solvers (coding assistants) a repo like this becomes a lot more meaningful.
- esikich 4mo agoYep and typically none of this is meaningful unless you have no security practices at all. You can't have it both ways. Every security team says these things are all critical even though, for example, it's only being used internally. Cool, so you somehow have our network cert, are on site physically, have compromised a laptop fully without all of our tools detecting weird shit, have a password, admin access to the repo, somehow are spoofing MFA, etc etc. Yeah it all adds up, but as an admin I'm just fucking done dropping everything for these kinds of things.
- grayhatter 4mo ago> At the time I post these, none have been reported. Feel free to report them yourself and take credit for the CVE if handed out lulz. I do this so to allure people into the field, and I've always found this is the most efficient way. I've been a skiddy, he would have believed this. Thankfully, I've grown a bit, and can see this for the transparent, "I'm angry and want to hurt others so I will feel a little less alone", it actually is. I'm sorry you're so angry dude (me too), but as someone who's joined the blue side, we'd appreciate it if you gave us some kind of heads up, the bad guys generally have a lot more time to scroll for new payloads than I do. Not all of us deserve the kindness of a heads up, but every single one of our users deserve it. Don't punish them because you're mad at someone else. You can flex on the idiots you're trying to flex on, without hurting people. Even an email to security@[that_project_domain] saying "hey, I've published these" would move you from the group of people I see making the world worse, into the group making it better. (You don't have to, obviously, but making the whole world worse wont make you less angry.)
- voodooEntity 4mo agoWhile i can follow your path, maybe because i see the same, i sadly have seen in groups of friends how this can go sideways very fast. If you report things, some companies gone treat you as a criminal/offensive actor and even go legal actions against you even you just tellem here you got this vuln. Sure you than can do it anonymous and so on but point is : its not like every actor that gets notified will react thankful to it. Some even just ignore it.
- esikich 4mo agoHow bad are your security practices that these tiny obscure things matter? None of these findings that show up here on HN should even make you flinch. The alarmist takes on this stuff is fucking exhausting and I'm tired of security teams bugging me about it. Do your job and this shit doesn't matter AT ALL.
- grayhatter 4mo agoI said "doesn't matter" to someone once... the resulting lesson came in the form of a reply from the whitehat researcher (waves, hi brian!) a 16step exploit chain resulting in a one click full account takeover. I'm equally annoyed and over the alarmist takes. But I don't think it's fair to group mine into it. I'm annoyed at seeing discard respect for others into the same void everyone is happy to toss quality. Do these tiny things matter? No, not to the default-panic-level everyone adopts when they see 0day, or CVE... but duh, I'm now just repeating exactly what you already said. That no, for the record is mostly because I don't use any of these, not just because they're boring exploits. While I always look, I default assume anything CVE is boring/pointless. But I still read them. But then, I'm not trying to convince the owner of the repo. I'm trying to discourage the theme among researchers that "no one cares", because I have seen researchers disclose bugs publicly, that we'd be eager to pay out on, because they disagreed with the decision on their last report. I've fixed bugs being actively exploited against our users, that was found/fixed only after a whitehat report for something adjacent (we pay on those btw, and you should too). I don't wanna live in the world where it's easier for the bad guys, the only way we get there is once "everyone knows", you gotta report the all bugs that you can turn into an exploit. I don't want "the whitehat researcher culture" to move towards, who cares' dump the PoC on github, screw anyone that could be hurt by the bad guys, they deserve to be punished for the incompetence of others. SWE's are shit at security, security researchers are shit at SWE, the only way we get the good outcome, is if they're willing (and encouraged) to work together.
- ok123456 4mo agoPretty unimpressive as security vulnerabilities. It would be better to just say these are simple bugs for the most part.
- unnouinceput 4mo agoall vulnerabilities are just bugs.
- stonogo 4mo agoBut not the other way around, which makes them different.
- void-star 4mo agoActually, Mudge of the l0pht (and later DARPA) once famously made the claim that all bugs are security issues waiting to be exploited in some way (I’m probably paraphrasing). I kind of agree. Although, the bugs on this dump are indeed mostly pretty lame, which is exactly what I’ve seen you get a lot of when you let an llm go bug hunting with no human vetting and confirmation in the loop. It’s possible/likely that whomever is running this experiment is keeping the non slop bugs to themselves. It’s probably what I’d do.
- stonogo 4mo agoSuch claims can both be true and pointless. For those of us who have to decide what actions to take, there is a point in differentiating between bugs and vulnerabilities, and breathlessly proclaiming "we found a vulnerability but we don't have an exploitation vector or proof that there's a meaningful security consequence" is annoying and likely to get the proclaimer ignored in the future.
- void-star 4mo agoThe context in which that statement was made, and in which I’m repeating it, I think, is just to say that any bug has the potential to be used maliciously. Ignore it, fine, but also don’t overreact to the intended message…
- bassiee 4mo agoI also have a library of bugs I found using Claude Opus 4.8 through the Customer Verification Program. Undisclosed, Atp I dont even know if they have been found by someone else. But just like this repo Theres a bunch of very specific scenario DoS bugs, buffer over/ underflows, that will get caught by ASLR and whatnot When I report serious ones, mostly the devs will respond with something like, yeah, thats how we designed it in a dangerous way, so that the layer above or below can solve the issues, and other footgun stuff.
- blincoln 4mo ago> When I report serious ones, mostly the devs will respond with something like, yeah, thats how we designed it in a dangerous way, so that the layer above or below can solve the issues, and other footgun stuff. This is one of the reasons that responsible disclosure exists. Their tune will likely change after sufficient bad publicity. If the Apache Solr devs can be convinced to add authentication to their product instead of hand-waving about reverse proxies or other add-ons, anyone can.
- jiug 4mo ago"Cibercrime is cringe"
- deleted 4mo ago[deleted]
- yuvrajsa 4mo ago[flagged]
- hypercain 4mo agoMythos has been achieved internally
- xlayn 4mo agoI want to rush to git clone, but as things are, the odds are extremely high that this kind of things that are too good to be real are honeypots and something there will compromise your machine or make your llm start working for someone else...
- GTP 4mo agoThen, don't rush and take a few minutes to set up a virtual machine.
- IncreasePosts 4mo agoWhat about all the virtual machine zero days?
- victorbjorklund 4mo agoBuy a VM in the cloud?
- necovek 4mo agoBut what about all the zero days in the payment processors ("buy")?
- ducktective 4mo agoNot even that, libssh2 vul. that "scp"s malware from cloud to your machine...
- midtake 4mo agoYou can just download the zip over HTTPS
- necovek 4mo agoWhat if it's leveraging a zero day in your zip or https library?
- dvt 4mo agoWent over a few of these with a pretty keen eye, and they aren't that particularly interesting. The Docker one is just a weird bug, it's not a vulnerability, and certainly not a "0-day" (which is a pretty loaded term and people expect bad stuff to happen). The nghttp2 nghttpx one is more interesting, and could potentially be used for phishing, but it's very hard to line up properly because the request queue is non-deterministic so basically impossible to target a specific victim (assuming proxy traffic). The VLC one is just a straight-up crash/bug. And VLC crashes all the time when using weird codecs, so that's nothing new. Am I missing something here?
- jeffbee 4mo agoI mean, that's how people get hacked. If vlc crashed on my computer, and every day I should raise thanks to my gods that I do not use vlc, I would immediately unplug it and thoughtfully consider the circumstances under which it would be safe to turn it back on.
- TheTon 4mo agoRight, this is why video parse / decode ought to be sandboxed. Writing secure code for these formats, especially in C, is really hard. I just sort of glanced at the bug in the repo, but it sounds plausible. It certainly wouldn’t be the first of its kind.
- tormeh 4mo agoAnd it's my impression the code is often in assembly, which is even less structured.
- Wowfunhappy 4mo ago> I mean, that's how people get hacked. ...when was the last documented case of an in-the-wild hack targeting VNC?
- ZeWaka 4mo agoVLC != VNC
- icase 4mo agooh-days for days
- zkmon 4mo agoAI is always a bit eager to report everything as an issue because the "number" of findings is seen as a measure of it's intelligence. Same happens with code review as well. It reports lots of non-issues. I suspect even Mythos output could have the same bloat, and the number (instead of severity) of the issues it reported could have scared people.
- dpark 4mo agoThis is not what I heard from folks who worked directly with mythos. I was told that the vulnerabilities it generated were largely real and meaningful.
- scottchiefbaker 4mo agoI'm an OSS developer and I've received three "CWE" alerts in the last two weeks. While they were all valid, they were for very trivial things like "this debug logfile could overwrite a file if it were a symlink" and "if a user is able to put OSC screen codes into the Git output they could write arbitrary data to the screen" These AI models are making *everything* sound like an exploit. Not sure if this is good for the ecosystem. It makes me question everything that comes in more carefully. Is this a real exploit, or someone farming for karma to claim "I opened 39 CWEs in the last week. Hire my 'security' company to audit your code."
- ibarrajo 4mo agoI’m sitting on a 0-day rce on the tizen browser (smart tv) Didn’t bother submitting since who actually uses tizen?
- huflungdung 4mo ago[dead]
- a-dub 4mo agocool to see rustdesk. low level memory bugs were long mysterious and i think often received most of the attention for this reason, but always fun to see reminders that "nope, good ol' fashioned logic bugs in high level languages have security implications too." if anything, i think they sometimes are more clever as they require deeper understanding of what the code actually does, intends to do and what was overlooked rather than the common set of bookkeeping errors that are often the root of the memory bugs.
- himata4113 4mo agoAh yes, the typical 'echo' command accepting untrusted user input 0-days.
- ozim 4mo agoI call fake or BS because Microsoft would be already on it.
- ozim 4mo agoI will consider it legit when in next 24 hours MSFT blocks it.
- shevy-java 4mo agoSkynet's strategy is to beat us into submission via spam slop.
- waynecochran 4mo agoDo NOT, under any circumstances, use any material in this repository maliciously. This is good-faith, open-disclosure vulnerability research intended to get more people interested in exploring this area of cybersecurity. Reminds of the message in the The Anarchist Cookbook before one the recipes that essentially said: "This is really dangerous, don't ever do it, here is how you do it."
- Aachen 4mo agoThe old book didn't say "... maliciously." though?
- waynecochran 4mo agoOf course not. You can melt things w thermite without being malicious. Like my friend's toolbox for instance.
- BizarroLand 3mo agoBut unless you have a level of chemistry experience that would put NileRed to shame, you cannot make drugs out of banana peels, and you really shouldn't even try.
- 0xroi 4mo agoThose all are fake AI gen text.
- chrismarlow9 4mo agoLooks like a bunch of re worded copies of existing CVE and a few new lower severity things. I only call them low sev because they seem to require the user to do things that are already inherently dangerous. Just my 2 cents from a quick scan. Edit: To be clear still interesting finds. I think with some chaining some of them might be more severe. Like the ovpn one and windows potentially registering vpn app as default open or some protocol opener for a url location like openvpn:// in an I frame and some clever social engineering. Just a random thought
- newguy33 4mo agoYea, that's what's confusing. some of these are like lower level slop but some are like genuine criticals. Floci, libssh2, c-ares, FFmpeg, and the PHP one are all LEGIT./ The Ghidra one for example, not so much. I cant help but wonder if this was halfway completed research folder and they just published it as is
- andai 4mo agoI wonder if LLMs can tell the difference. Maybe it's like back in the day when you had to add "+good -bad" because otherwise it wouldn't know you wanted it to be good.
- smsm42 4mo agoPHP one is at best a moderate-level bug in SOAP client which I don't see any realistic way to exploit (the whole convoluted setup in the POC assumes PHP execution access, which begs the question why bother if you already can execute arbitrary code?) - does not look like "genuine critical" at all.
- newguy33 4mo agoCritical is an overstatement but it userland PHP execution does not equate to native process control. There are many situations where an attacker may have constrained PHP execution, gadget execution, template or plugin execution, deserialization reachability, or a sandboxed context, but not arbitrary native code execution or arbitrary memory write. Definitely impactful
- ChuckMcM 4mo agoLooks like someone is running one of the LLM models and publishing the results. It looks that way because there is a really wide mix from things that are silly "replace system binaries to run arbitrary code!" to things that could be legit. That is kind of par for the course when you ask an LLM to 'find an exploit and write a PoC' kind of prompt. Presumably if you train something on the last 15 years of Metasploit[1] reports it can find the same bugs that people have written into new code. [1] https://en.wikipedia.org/wiki/Metasploit https://en.wikipedia.org/wiki/Metasploit
- phs318u 4mo agoI get the sense that folks here are assuming this could be the work of an AI practitioner or bot dumping a bunch of exploits. Assuming there are some serious exploits in this trove, what would the motive be to do it in this way - without reaching out to the various code maintainers in some way?
- deleted 4mo ago[deleted]
- xbmcuser 4mo agoBugs are bugs security vulnerablities or not it's good for open source project when someone actually goes through the code even if it is with an llm. As most people assume someone has gone through the code when it might not be true.
- kevinten10 4mo ago[flagged]
- TallGuyShort 4mo agoThis is common in the hype era of AI models that can look for security bugs. An open-source project I used to work on that is basically "distributed code execution as a service" keeps getting reports that the job submission function is a vulnerability. The reporters don't even understand what the project does.
- blincoln 4mo agoIs the job submission handled securely? I've seen plenty of systems along the lines of what you're describing where unauthenticated clients can submit jobs. Sometimes the developers even claim that's intentional. Either way, it's a vulnerability, because it compromises the underlying hosts.
- TallGuyShort 3mo agoYes, and that's not what people are reporting flaws in. The reports are "this daemon accepts arbitrary code and then runs it!"
- smsm42 4mo agoPHP one appears to be a convoluted way of executing arbitrary code on a local server conditioned on the ability of already executing arbitrary PHP code. In other words, not a security issue at all. The cookie parsing issue might be a bug with security implications if you talk to hostile SOAP servers (didn't look deeper into it but it's plausible) but I can't see how it can be effectively exploited without having a level of access on the target server which makes the whole exploiting question moot.
- sampli 4mo agoSome skid that bought a GitHub account (real word username) and just let fable go nuts on stuff without actually proving it on real applications
- reinitctxoffset 4mo agoThe only thing with a worse inflation story in 2026 than the United States Dollar is the Zero Day. Used to be a zero day got you unauthorized access to a computer system with no warning. Now it might not even get a maintainer to do a patch when they're bored.
- squeegeeninja 4mo agoIt seems like we are watching the newest form of the script kiddie evolve in real time (no offense intended towards the author, everyone starts out young). It's going to be interesting whether this evolves into its own thing or just ends up being the same old dynamics but with a new set of tools.
- microgpt 4mo agoDoesn't GitHub require phone number these days? Shouldn't be hard to trace
- consp 4mo agoOf course no services to fake this exists or have existed. I mean, a well determined person can het around such issues.
- microgpt 4mo agoWhen you fake it it's still registered to someone and that person is liable for whatever crimes are committed under it. Or at least that's how it works in most of Europe.
- Ozodbek1337 4mo agoI'm sure this account owner reported them to vendor and after getting rejection researches uploaded here many of exploits written by AI
- Ozodbek1337 4mo agoI think attacker received rejection from vendor some of them duplicate some of them N/A after this account owner published them many of them written by AI not by real researcher
- 2432412341 4mo ago[flagged]
- Manishearth 4mo agoI recently used a pretty well-tuned LLM to find ~500 safety bugs across the Rust ecosystem. Most of them are minor, and even major safety issues in Rust usually mean "it's possible to accidentally use this API in a way that is broken" not "this is directly exploitable", but I didn't want to just file LLM output as issues on these repos. I very briefly considered doing something like this: if I just post the results on the internet, people can crowdsource filing issues and working on fixes. It's certainly not the nicest way of doing this, but on balance I'd like these issues to be fixed eventually. I ended up not doing that and am instead filing a couple issues a day because it's not that much of a burden. This was an experiment that was much more successful than I expected, so I didn't budget to spend this time, but it's also not a huge deal to slowly do it.
- Aurornis 4mo agoCan you at least provide some links to examples of the issues you’re filing? I’ve seen so many claims of people who used LLMs to generate hundreds of issues that turned out to be full of hallucinations or non-bugs being described as bugs that any claim like this needs some real evidence. Saying you found 500 safety bugs in Rust but that you’re casually only filing a couple of them makes this hard to believe.
- blazespin 4mo agoI have a dozen or so critical CVEs now, it's not hard to believe at all if they're just hardening tasks. I can get a dozen hardening tasks from just one prompt. I don't even bother filing them as the critical ones are more important right now.
- asqueella 4mo agoDon't let the hype turn you into a cynic. You're replying to a Rust core team member, who explicitly says the issues are mostly minor, across Rust ecosystem and not in Rust itself, and that they're filing them manually to avoid dumping unreviewed AI output on people. It's easy to find the 37 issues they have already filed: https://github.com/search?q=soundness+gemini++author%3AManishearth&type=issues&ref=advsearch&s=created&o=desc https://github.com/search?q=soundness+gemini++author%3AManis...
- simonpure 4mo agoThe readme was recently updated. > In regard to AI usage, my fuzzing workflow was automated by AI with a strict harness. I used GPT-5.5-3-Codex-Spark for ALL the fuzzing, as barely any "thought" is necessary when provided with an efficient harness. Contrary to the growing narrative that I'm just some random child burning tokens, I DO actually have a degree in the subject and have published multiple papers on fuzzing methodology. I spent years researching and developing new tools and ideas for how to fuzz. You do NOT need a SOTA model to help you identify these issues, I promise!
- zftnb666 4mo agoSomeone's last day at their job is going to be everyone's last day at their job.
- deleted 4mo ago[deleted]
- deleted 3mo ago[deleted]
- the_rz1027 3mo agoI have a correction for CVE-2026-20896 (Gitea trusted-proxies / X-WEBAUTH-USER) was not part of this dump. It was reported by @rz1027 (me) as in Gitea's coordinated 1.26.3 security release, credited in the release notes. The exploitarium's actual Gitea PoC is a different bug (act_runner container-options escape). Refs: [https://blog.gitea.com/release-of-1.26.3-and-1.26.4/ https://blog.gitea.com/release-of-1.26.3-and-1.26.4/] [https://github.com/go-gitea/gitea/security/advisories/GHSA-f75j-4cw6-rmx4 https://github.com/go-gitea/gitea/security/advisories/GHSA-f... ] [https://hivesecurity.gitlab.io/blog/gitea-forgejo-nine-cves-1263-security-release-2026/ https://hivesecurity.gitlab.io/blog/gitea-forgejo-nine-cves-...].