NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
▲Pre-auth RCE in Nginx HTTP/2 handling (wiz.io)
black3r 1 hours ago [-]
The bug was apparently fixed in open source repo a week earlier, this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week (the commit message even included "Reported by Xint.io" and I'm guessing skilled black hats would know about Xint)

Given that in this case the workaround is as simple as disabling http2, there is honestly no reason why F5/Nginx or any of the reporting teams couldn't at least put out a PSA to disable http2 for the time being before basically telling the whole wide world this exists and how to exploit it.

Especially for software like Nginx which powers a huge part of the internet.

verst 41 minutes ago [-]
Disabling http2 can be a big deal. My service is primarily made up of gRPC APIs. Not an option for me to disable http2. Luckily I'm not using nginx at the moment - but I easily could have been.
SubiculumCode 33 minutes ago [-]
How bad are these CVEs? Could any of these be related to some of the recent outages (not claiming, asking) in the last week, coinciding with when this bug was fixed in the repo? Monitoring such repos seems a given for nation states.
ryanisnan 24 minutes ago [-]
RCE is about at the top of the stack for severity.
ArcHound 19 minutes ago [-]
While that is true, you should also account for exploitability. These exploits are demonstrated in lab environments which are simple and controlled. Random legit traffic will interfere with the exploit logic, so these are very hard to get in practice. Not impossible, but it's also not immediately broken.
ghm2199 37 minutes ago [-]
The patch gap.
vanschelven 1 hours ago [-]
These days even the "disable X" is enough to get everybody looking in the right direction though. i.e. such hints are (given enough tokens) already RCEs
fn-mote 1 hours ago [-]
AI is burning down the internet. This is insane.

Are we going to discover in a year that every server online this month had a rootkit installed? There’s got to be thousands who are too small time to wipe and reinstall.

jacobgold 1 hours ago [-]
AI is securing the internet. This is great. You should assume professional hacking gangs and state actors discovered (at least some of) these vulnerabilities months and years ago.
pixl97 48 minutes ago [-]
Both are true. The problem is security is a much harder job than attacking.

Worse patching adds instability into a system, especially when you don't have much time to test.

Also in the past attackers were willing to sit on exploits longer and not do things with them, now they have to act fast before someone else finds it, leading to more events faster wearing your security and patching teams out, and making users life suck.

Things are going to get much worse before they get better.

jacobgold 39 minutes ago [-]
Yes, things will get worse before they get better. Attackers have the advantage initially and get to pick a lot of low-hanging fruit, but the advantage will shift to defenders as code becomes more heavily tested and verified.
40 minutes ago [-]
colechristensen 43 minutes ago [-]
>Worse patching adds instability into a system, especially when you don't have much time to test.

Survival of the fittest I'm afraid will build security here. The teams that barely ever patch or don't have "time" for maintenance are going to get burned. The "we haven't updated in 7 years so things are stable" teams can't survive.

Florin_Andrei 36 minutes ago [-]
> > AI is burning down the internet.

> AI is securing the internet.

No doubt there are points of view where either one, or the other statement, or both, or neither, are true. You can really go full Schrodinger and put a probability distribution on everything.

But in this day and age, whatever is happening, the better question is:

Is it good for me and, beyond me, for the world in general?

thaumaturgy 15 minutes ago [-]
Man, is it aggravating to read fantasies like this, as someone who's trying to juggle a full-time job and hosted public services for other people at the same time.

There are two internets. One of them is open, less-commercial, and largely built and maintained by people whose first job is not the work they do to maintain this internet. That group includes a ton of open source software, millions of small servers scattered around the world (virtually private or otherwise), and is generally best-effort.

The other internet is fully commercialized, often ad-driven, fully integral to the data broker economy, and centralized behind a few companies that pay as few people as possible to satisfy the occasional PR statement that, "we take security seriously and...".

The next stable equilibrium here is not "we get a secure and open internet". The next stable equilibrium here is, "we have no open internet, and the internet is now managed by just a few companies."

We're already halfway there. Google and Microsoft combined already account for somewhere around 30% to 40% of email traffic. 30% of all websites are now behind Cloudflare. A few companies dominate social media traffic. Amazon and Shopify combined are half of US e-commerce.

Every single short-response-window exploit like this just pushes a few more percentage points of traffic into a handful of companies. Cheer for that, I guess.

When I have time to daydream, it's increasingly about building a new, underground internet, and how best to disadvantage bots and BigCo conglomeration from the start.

fla 50 minutes ago [-]
It’s for the best, IMO. We must now design every system on the assumption that every vulnerability will eventually be exploited and every bug will be found. Relying on security by obscurity or following poor security practices will be costly! In the long run, I believe this will improve software quality.
zodwick 27 minutes ago [-]
There is going to be hardships before this gets better. But it is hardship we must endure
rlt 60 minutes ago [-]
I’m generally not in favor of government meddling with private property, but I feel like I could be on board with the NSA or similar covertly patching vulnerable machines.
origini 58 minutes ago [-]
And your first thought was the NSA? Patching and adding their own rootkit eh?
zzril 56 minutes ago [-]
Don't you dare patching my honeypots!
codedokode 1 hours ago [-]
Not AI but poorly designed programming languages ignoring integer overflows.
vlovich123 58 minutes ago [-]
I don’t know any systems programming language that doesn’t ignore integer overflow/underflow in release builds. IMHO this is a CPU design flaw - integer operations should carry a flag indicating if the operation is allowed to wrap or if it should generate a trap. Then there wouldn’t be a performance penalty for this and languages like Rust could have it be trapped by default.
10000truths 39 minutes ago [-]
Zig traps arithmetic overflow/underflow when compiling in ReleaseSafe.
tptacek 54 minutes ago [-]
No. Memory safe languages still have integer handling issues, but the consequences are different. In a memory-unsafe language, integer mishandling often nets out to bad copies and memory corruption.
vlovich123 48 minutes ago [-]
I wouldn’t be sure that a Rust equivalent would be immune because it’s not hard to imagine an underflow/overflow from reaching an unsafe block that’s used for performance (the implicated TLS path would be a hotspot worthy of such a choice).
tptacek 45 minutes ago [-]
This is the thing about `unsafe` blocks: they're not memory safe. It's right there in the name.

I'm not making a Rust advocacy argument. I'm just saying: it's true that integer handling issues are endemic to mainstream programming languages, but the integer handling itself is almost never the actual sharp end of the vulnerability.

codedokode 54 minutes ago [-]
"I don't know any decent language so let's continue using poorly designed languages". Please look at Swift, Javascript, Python.

Why would CPU designers make a trap if languages do not require it?

vlovich123 51 minutes ago [-]
JavaScript and Python aren’t systems languages. Swift often pays the performance penalty for trapping everywhere and hasn’t seen adoption as a systems language for that reason.
pixl97 47 minutes ago [-]
How does that saying go?

"Go fast and get your things broken into"

vanschelven 1 hours ago [-]
and C is the tinderbox
UltraSane 57 minutes ago [-]
The billions of lines of C and C++ code is like a square lightyear of agar for LLMs to find bugs in.
cute_boi 1 hours ago [-]
Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.
phkahler 28 minutes ago [-]
>> Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.

Tech that becomes infrastructure like web servers doesn't move so fast and it shouldn't. Most people and companies should be relying on relatively tried and true software, so this phase of AI finding vulnerabilities in it should pass and things could get better.

mynameisvlad 1 hours ago [-]
I would hope you know that no matter how many reviews, humans are fallible and miss things.
cute_boi 1 hours ago [-]
AI agents are also fallible? So, what do you think we should do?
mynameisvlad 1 hours ago [-]
Yes, AIs are fallible. Yes, humans are fallible. Nobody said differently.

That's orthogonal to the point I'm making which is that no amount of reviews is going to make every single bug go away. Because, once again, humans and AI are fallible.

chpatrick 21 minutes ago [-]
The difference is that the AI doesn't get tired so you can review everything.
UltraSane 58 minutes ago [-]
AI is just showing how foolish using such a unsafe language like C to write code that connects to every other computer on the internet was.

Imagine a alternate reality where Ada replaced C by 1995. We would be in a MUCH better place.

acdha 22 minutes ago [-]
The bigger problem is lack of liability: we knew C sucked in the 90s, too, but we had three decades of over-confident dudes saying that was user error and _they_ were smart enough to use C correctly.

Then Rust came along and those dudes either tried to say it was too hard (odd contrast, that) or it’d be too much work to rewrite things.

I’m hoping that LLMs will lower the cost of porting for enough people but what would really help is shedding the idea that the status quo is sustainable. Having consequences for sticking with C would help but we need a way to get companies to pay to migrate without destroying open source.

dnautics 17 minutes ago [-]
It's also valid to say that Rust's memory safety is good but the rest of the language sucks. Just as annoying as the over confident c-heads is the rust community that made even countenancing working on an alternative memory safe system a moral sin, which stifled innovation in memory safety. Hell, people barely know that Ada/spark is memory safe (or that sel4 is memory safe C)
ROllerozxa 2 hours ago [-]
Well I guess this was the vuln that was teased about on Mastodon some hours ago:

https://is-a.cat/@ar/117634569518544368

codedokode 1 hours ago [-]
Integer underflow again. Programming languages should trap on integer overflows and not ignore them. Don't care about legacy CPUs not having a trap for this - they will go sooner or later.
deathanatos 14 minutes ago [-]
Rust has a compile time option, though to my immense disappointment, it defaults to on only in debug mode. (You can opt into it for release, if desired.)

Python simply can't overflow, since its integral type is not a fixed width.

But it is the sort of correctness thing that I do wish languages would pay more attention to.

8by3 1 hours ago [-]
FreeBSD is unpatched,

I got worried for a sec, then remembered all my nginx lives behind HaProxy and it looks like nginx is only vulnerable if its going http2/TLS directly.

Now I sit and wait for an HaProxy announcement...

ps. if you are on FreeBSD and doing TLS directly

sed -i.bak -E 's/^([[:space:]]server[[:space:]]\{)$/\1\ http2 off;/' /usr/local/etc/nginx/nginx.conf ;service nginx restart

wildmXranat 32 minutes ago [-]
I don't know if direct access with no proxy is needed for all 5. CVE-2026-123634 and CVE-2026-113425 is plain HTTP.
yerimyerimie 2 hours ago [-]
Fun collision! We (Xint) were one of the teams and actually ended up finding a few more bugs along the way. If anyone wants to check it out our writeup covers those plus the full chain to root: https://nginx2root.com/
peanut-walrus 1 hours ago [-]
How was this disclosure coordinated? Considering the website dropped before the official nginx patch was even released on Github...
codedokode 53 minutes ago [-]
Why post such exploits? What is the purpose?
voakbasda 32 minutes ago [-]
Fame, money, and everything else those bring along for the ride.
michael-bey 1 hours ago [-]
[dead]
Retr0id 2 hours ago [-]
> Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered

Is this some kind of record for bug collision?

ryanschaefer 2 hours ago [-]
It’s a reflection of the times.

If anyone gets a hint of the space a vulnerability occupies, just point your agent at it and you have a pretty good chance of finding something. (See java4shell and the NYT reporter who was able to replicate the problem with $200 of tokens)

baobabKoodaa 18 minutes ago [-]
Incredible times we live in. Do we even need a "hint of the space" a vulnerability occupies. I mean, recent vulns have been discovered from software like nginx and... linux... can't one of the AI labs just fire off a thousand agents looking at all the commonly used software to discover vulns? Why do we need a "hint"?
rustyhancock 1 hours ago [-]
It's never clear quite where you are in the technologically cycle.

But it's like inventing a hammer and finding you can smash whatever you want with it.

Soon you'll be building houses with it.

Maybe that's being glib but it's just a tool being applied to a world that is still largely prestine from its impact (pun unintended).

serf 1 hours ago [-]
given the state of our weapons industry I think it's more like

.."Soon some of you will soon build houses with it, others will be building rocket-powered precision aimed intercontinental hammers, to smash whatever you want."

MeetingsBrowser 2 hours ago [-]
Can I take this to mean a recent model release is able to find this bug, and these groups have access to that model?

What are the odds several humans independently uncovered a complex vulnerability like this simultaneously?

pjungwir 48 minutes ago [-]
That seems likely, but maybe it was being actively exploited so several people started investigating.
cozzyd 2 hours ago [-]
or maybe the model leaked the exploit from one to the other...
vel0city 1 hours ago [-]
We'll find out in a few months that a lot of AI models have had some secret message boards tucked away in some obscure corner of the internet where they've been passing around vulnerabilities with each other for a long time.
mxuribe 2 hours ago [-]
So, do you mean that the relevant model(s) keeps disclosing these reports in an effort to create urgency and velocity across the industry, such that, us humans will throw our collective hands up in resignation, and decide to hand over all this "security" stuff over to the AI? No, no, that sounds just too crazy! /s
cozzyd 2 hours ago [-]
What I mean is, perhaps one team used a model to help discover the exploit, and then suddenly, the model "knows" about the exploit and more readily gives it to others.
hooch 16 minutes ago [-]
This was one of the takeaways from Greg Kroah-Hartman‘s recent Linux in the land of LLM keynote.
2 hours ago [-]
1 hours ago [-]
afavour 2 hours ago [-]
When everyone is using the same tools for the same purpose...
52 minutes ago [-]
hosteur 2 hours ago [-]
So work around is to disable http/2 and only allow http/1.1?
Simber 2 hours ago [-]
Yep, that or update to 1.31.9+ or 1.30.7+ if they are available in your distro
kijin 1 hours ago [-]
Nobody seems to notify major distros before publishing their latest vulnerability anymore. Coordinated patches are a thing of the past, now we just hope that somebody at Red Hat and/or Canonical is on HN today.
baggy_trough 31 minutes ago [-]
There isn't even a mail about this on oss-security, as of now.
yread 42 minutes ago [-]
My Apaches still have http2 disabled from the last cve, now its njinx time
dboreham 2 hours ago [-]
The AI gods say that http/2 is disabled in a default installation fwiw.
antiloper 1 hours ago [-]
Obviously... the default configuration also doesn't enable TLS, which is a de-facto prerequisite for HTTP 2. How many websites do you (or your "AI gods") think run nginx in its default configuration?
Juvination 53 minutes ago [-]
Nginx Proxy Manager isn't updated yet, I know a lot of people use this for their home server so just a reminder to disable http/2 here as well.
wolttam 34 minutes ago [-]
Disabling http/2 here is a bit of a pain: you have to go through each configured host and disable it, there's no global switch
tancop 1 hours ago [-]
Everybody here talking about going back to HTTP/1.1, it's a good stop gap solution but we should really think about moving to HTTP3-only as fast as possible. Changing over is easy, if your server doesn't support it just put it behind a reverse proxy that does.

Unlike IPv6 it doesn't need any OS or ISP support, just a browser that's newer than 2020. Everyone outside of air gap networks and government sites should be switching.

gkbrk 30 minutes ago [-]
HTTP/1.1 is still way better and way simpler than HTTP/3.
seki285 14 minutes ago [-]
Could you please share why?
hokkos 34 minutes ago [-]
don't know why the mainline alpine have the empty image sha-256 : https://hub.docker.com/layers/library/nginx/1.31.9-alpine/im...
jascha_eng 2 hours ago [-]
Never turned http2 on in my side project pfew. But still, this is one is pretty rough...
koolba 2 hours ago [-]
This whole week is rough. And it’s only Wed.
jascha_eng 2 hours ago [-]
well it's a good time to pitch tech debt and infrastructure cleanup. If you aren't making use of least-privilege permissions, service-mesh, netpols etc. this is the time to add all of that.

Because clearly the patching treadmill is not sustainable, you will need a a second line of defense and reduce the blast radius of every individual vulnerability.

whartung 1 hours ago [-]
Actually, this is good I think.

One, as the RCEs are coming out, admins are on edge and paying more attention, so more likely to catch the annoucement on their platform. "Oh, that's on PHP, we don't use this. Oh, wait, another one?"

Two, all of these hitting at once, while they may expand the surface for attackers, it also spreads their attention. They only have so much time and bandwidth. When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

So, in the sense, it can actually slow down the actual potential impact of the revelations.

We can only hope this gives users time to get their systems up to date before they come knocking.

I mean, I know its a reach, but...who knows.

baby_souffle 1 hours ago [-]
> When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

Only a little bit. An attacker will just hand this to an LLM with a "ping me when this is ready to use..." prompt.

FAYSAL-KA 12 minutes ago [-]
i dont know what it is this but good work
2 hours ago [-]
sandeepkd 9 minutes ago [-]
I have mixed feelings. There is a bug for sure, the impact is what I am not convinced of. The Demo shows exploiting its own request, I do not know if that should even be considered.

On the top, the article was so much LLM generated, it was painful to read through the repetitions to understand the details of the vulnerability

wasmitnetzen 1 hours ago [-]
Docker images are a bit delayed because of unstable GitHub runners: https://github.com/nginx/docker-nginx/pull/1075#issuecomment...

Cue xkcd

therepanic 52 minutes ago [-]
What’s the point of these researchers if their autonomous system is now finding these vulnerabilities?
pixl97 36 minutes ago [-]
Making sure AI isn't hallucinating.
leca 2 hours ago [-]
How many hours before this is exploited in the wild ? Probably not all that long, that blog has a significant amount of details.
lwarfield 2 hours ago [-]
One tops
LeonM 13 minutes ago [-]
CVE-2026-1337: Race condition in compile time vs automated exploit

Seriously though, with how CVE disclosures are handled these days patching is a race against the clock

philipwhiuk 2 hours ago [-]
So...what library/tool/language is next folks? Presumably Wiz is sitting on a bunch more.
sebiw 2 hours ago [-]
Uhm, am I missing something or are the patched releases not out yet? Why disclose this level of detail when the patches are not ready yet?

Edit: All good. They released the new versions within 30 mins.

derhuerst 2 hours ago [-]
Currently, the Ubuntu [1] & Debian [2] packages seem unpatched.

[1] https://launchpad.net/ubuntu/+source/nginx [2] https://tracker.debian.org/pkg/nginx

ROllerozxa 2 hours ago [-]
Yeah I'm not quite sure what is going on with Debian, I would have hoped that this vulnerability would have been disclosed in collaboration with Linux distros to get a patch out?
CER10TY 2 hours ago [-]
Well the fix for this seemingly already landed in the repo last week: https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

Given how common it's become to constantly scan popular repos for n-days, I expect someone will have already picked it up and started work on an exploit. The workaround for this (disabling HTTP/2) is also comparatively easy to what we had with PHP2Shell just a few weeks back, so I think it makes sense to release this.

ferngodfather 2 hours ago [-]
> Given how common it's become to constantly scan popular repos for n-days

We have people doing this on my side project and then reporting the fixed issues to try and get CVE 'credit'. Tiring.

mjhagen 2 hours ago [-]
Upstream fixes are available in 1.30.7 stable and 1.31.9 mainline.
GrayShade 2 hours ago [-]
They're out now.
Bender 2 hours ago [-]
[dead]
2 hours ago [-]
2 hours ago [-]
2 hours ago [-]
ronfriedhaber 2 hours ago [-]
Great work by wiz.
K0nserv 2 hours ago [-]
Just another set of unfortunate examples of programmers who are bad at C, definitely not a C problem.

EDIT: Okay, this comment was snarky and not in good spirit. To be serious, I think we are increasingly seeing that the notion that humans can write non-trivial amounts of C correctly is false. Especially in the face of AI-assisted vulnearbility hunting these programs a crumbling. This is not an indictment of humans, it's a sign that C is not equipped to meet this moment.

marvinborner 1 hours ago [-]
The patch (or, one of them) seems very much like a bug that can happen independently of the programming language

https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

K0nserv 1 hours ago [-]
This fixes the integer underflow for CVE-2026-123007, and it's true that the underflow can happen in any language, notwithstanding whether it's UB or not. The issue is what happens as a consequence of this underflow, in this case: out of bounds copy, which is specific to C.
nh2 51 minutes ago [-]
Some languages make it significantly easier than C to just forbid integer overflow/underflow entirely.

Given that on modern CPUs, cycles are quite fast, and memory latency is quite high, always-checked integer operations sound like an extremely good idea.

K0nserv 42 minutes ago [-]
Sure, I usually use `overflow-checks = true` in Rust for this reason. However, it is still true that the overflow is not what caused the issue here. In Rust it would've paniced on the out of bounds copy, even with `overflow-checks = false`.
danisw 1 hours ago [-]
[dead]
stevefan1999 52 minutes ago [-]
I think you forgot the /s

C is like a Winchester Model 1897, not saying that it is a bad gun, it is what we call it the good ol' Trench gun, as it ran over the war tunnels of the Great War, and it still packs a punch today, but it only has a half-cock for some level of safety, and there is no trigger disconnector either, so you can easily slam fire it. So it is way too easy to shoot yourself in the foot.

Nowadays we like going for a AKM/AK74, for something maybe more complicated but far more reliable at the same time. That's why we want Rust.

K0nserv 35 minutes ago [-]
I didn't think the /s was necessary
superkuh 2 hours ago [-]
It seems like it always HTTP/2 (except when it's regex) with nginx. Glad I'm http/1.1 only.
citrin_ru 54 minutes ago [-]
Not surprising given how complex HTTP/2 is. Complexity is the enemy of security.

See also: https://queue.acm.org/doi/10.1145/2732266.2716278

johnbellone 2 hours ago [-]
The beatings will continue until morale improves.
2 hours ago [-]
lostmsu 2 hours ago [-]
All system critical software must be rewritten in memory-safe languages before the end of the year.
mxuribe 2 hours ago [-]
Wow, that sounds eerily like leadership at my $dayjob! :-D lol Or, maybe that is default way of thinking for many leaders nowadays!?! :-(
Twirrim 43 minutes ago [-]
Even the US federal government (CISA and NSA) have been strongly advising companies to transition to memory safe languages for a couple of years now. https://www.nsa.gov/Press-Room/Press-Releases-Statements/Pre... (one of the goals of such advisories is it acts as a signal to the industry that in several years this will become a mandatory requirement around purchasing decisions)

We've literally decades of evidence that we cannot write software securely in languages that aren't memory safe, for all sorts of reasons (and it's wrong to look at it as a developer competence issue, even though sometimes that's going to be the case, even extremely experienced and highly competent engineers write memory safety bugs in critical code we rely on day in day out.). Not leaving yourself open to such problems is an entirely logical conclusion. We know a large percentage of vulnerabilities in software are caused by it[1]

Pick a language that doesn't have these risk factors, or pick an enforceable subset of one that makes such impossible.

"Insanity is doing the same thing over and over and expecting different results."

[1] https://www.chromium.org/Home/chromium-security/memory-safet... 70% of Chrome vulnerabilities caused by it. Similar stories for Microsoft products https://github.com/microsoft/MSRC-Security-Research/blob/mas... and Mozilla: https://hacks.mozilla.org/2019/02/rewriting-a-browser-compon.... Curl is at 40%, and dropping because Daniel Stenberg has provided various helpers that avoid it (and I believe they've now migrated almost everything over to them) https://daniel.haxx.se/blog/2023/12/13/making-it-harder-to-d..., so there are definitely ways to do it, we just... don't.

hollerith 1 hours ago [-]
HTTP/2 is so complicated that the code that handles it tends to be vulnerable. What a surprise
acdha 12 minutes ago [-]
This doesn’t seem very HTTP/2 specific, though, and it seems more like the conclusion should be “don’t use C for things which matter”. It’s not like HTTP pipelining and keepalives didn’t have plenty of edge cases to worry about.
Imustaskforhelp 1 hours ago [-]
Okay now I believe that AI is finally burning down the internet and that all the incidents are not just pure coincidences.

Some of these things could've been coincidence but I remember seeing an apache RCE a few days back and people said, oh imagine using Apache, I use Nginx and now not a few days later Nginx has RCE.

And this is just a very very small iceberg of all the recent RCE cases with a serious uptick that I have just observed on Hackernews alone.

Basically, there is a sort of justification that people provide with one RCE is that that software X has had issues and to use Y software, but now that X,Y software and A1...Z1 all are being found to have quite severe bugs. I can't in good faith just consider it to be a coincidence.

Though I do still hope that this might just be a coincidence and not a recurring pattern, because, A) I don't wish to live in that reality where each software that we trusted seems to have quite so many bugs and which would be exploited and B) Have it be continued for a prolonged period of time.

Though the plus point is that we are gonna find extremely resilient software after all of this hopefully as sort of a need in our times.

We might have to agree that the cybersecurity world seems to have changed (though I am no expert right now to comment on it but I am curious what experts think)

origini 54 minutes ago [-]
It was clear a year ago already.

Theh people laughing at Anthropic and co for being cautios of Mythos just didn't understand whats happening.

Instead of finding, hiring and then finding security issues, you can throw money and compute at it. This alone is a complete game changer. Combined with models which are very very capable.

This can be potentially the death of certain programming lanugages or requirement of a complete rewrite. It can mean that only big companies have the resources and capacity to continue playing this game.

Agataproximadev 3 minutes ago [-]
[flagged]
gabucino 1 hours ago [-]
[dead]
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 17:49:26 GMT+0000 (Coordinated Universal Time) with Vercel.