Friday Squid Blogging: Pacific Flying Squid Populations Dropping in Korean Waters
Climate change is the issue.
As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.
Climate change is the issue.
As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.
ResearcherZero • November 14, 2026 2:04 AM
China is taking a crack at attempting to make battery swaps work.
‘https://www.theguardian.com/environment/2026/nov/12/china-battery-swapping-e-trucks-catl-ev-range-anxiety
How a battery swap might work if the housing is not replaced.
https://edition.cnn.com/2023/12/08/business/tesla-battery-swapping-stellantis
ResearcherZero • November 14, 2026 2:16 AM
@Travis
The article can be found at the link highlighted in red (the issue).
–
Maintaining a battery swap station is a nightmare, with significant financial risk.
Would you like someone else’s beat up old battery pack that is not well maintained?
Ample, the company behind a modular battery swap system, filed for Chapter 11 bankruptcy.
https://electrek.co/2025/12/19/another-ev-battery-swapping-company-is-going-bankrupt/
Swapping out an entire Tesla battery pack that weighs more than 1000 pounds?
https://www.latimes.com/business/autos/la-fi-hy-tesla-battery-swap-harris-ranch-20150310-story.html
The process of swapping a stationary, household battery remains expensive and complex. It is much cheaper than a household coal-power plant, or small, modular nuclear reactor, even with the added cost of rooftop solar and extra expense of installation and maintenance.
As long as you can find someone willing to do the job.
https://tech.yahoo.com/home/articles/homeowner-says-tesla-approved-battery-213400812.html
Dancing On Thin Ice • November 14, 2026 9:13 AM
The flight stoppage on Friday November 13 was the day after the FAA announced they are phasing out using floppy disks to update their systems.
There have been discussions here on the security risks/benefits of using physical media to maintain systems.
lurker • November 14, 2026 2:06 PM
@ Dancing On Thin Ice, ALL
There’s an interesting “he said, she said” at the Guardian, including
“I want Congress to give us emergency funding,” Duffy added later. “I want $50bn. President Trump is a builder. He is going to build this network, and deliver for the American people.”
https://www.theguardian.com/world/2026/nov/13/faa-ground-stop-flights-explained
lurker • November 14, 2026 10:28 PM
Italian regulators have fined social media giant Meta €805m (£670m; $887m) for accessing Android users’ photos without their specific consent.
– https://www.bbc.com/news/articles/cwn83gxemk35o
Some people never learn – using photos without consent is why he suddenly left Harvard …
Dancing On Thin Ice • November 14, 2026 11:40 PM
@ lurker As an amateur security person, I got the predictable amateur results by not considering other security issues of false flags, and creating FUD by officials that have lost the trust of much of the public.
The funds to fix the issue were opposed under a previous administration by those now seeking the money on top of what is being spent on vanity building projects.
(Sorry about the doublw post, there was a glitch in the posting system throwing up an error message to try again.)
Clive Robinson • November 15, 2026 2:22 AM
@ Bruce, ALL,
In last weeks Squid, In the comment I made about the “Criticale RCE found in Apache” vulnerability
I also made comment about CVE numbers likely to hit 145,000 by years end. Based on the CVE number of the vulnerablity giving a count so far this year giving us about 400 new vulnerabilities a day.
I then went on to mention AI’s part in this significant rise, that is beyond the ability of single individuals to keep up with.
But more importantly how AI via less than bright management will decimate experiance in ICTsec.
Well on reading The Register I see that Friday 13th US time about a day UK time they commented,
This year’s bug count just passed 100K
‘We don’t have a security problem anymore. We have a data problem now’
“Chalk up a new record for vulns. The number of Common Vulnerabilities and Exposures (CVEs) found and disclosed so far in 2026 surpassed 100,000 on Friday – more than double 2025’s total – and the reason can be summed up in two letters: AI.
“It’s kind of wild,” Josh Bressers, VulnCheck’s director of coordinated vulnerability disclosure, told The Register. “The thing that almost scares the bejesus out of me is while 100K sounds like a lot, in a couple years we’re going to say, remember when it was only 100K?”
As of the time of our interview, about 4 pm UTC on Friday, VulnCheck counted 100,222 CVEs, he said. Microsoft alone added 1,094 security flaws to the total count on Tuesday, following 1,474 vulnerabilities the month before.
“There’s no denying the fact that vulnerability hunting with AI is driving a majority of what we’re seeing.” All the major CVE Numbering Authorities (CNAs) – these are the organizations authorized by the CVE program to assign unique identifiers to security vulnerabilities – like VulnCheck, Microsoft, Oracle, GitHub, and other large enterprise IT vendors “are just screaming into the atmosphere right now,” Bressers said. “It’s AI.”
“
https://www.theregister.com/security/2026/11/13/this-years-bug-count-just-passed-100k/5309882
Whilst I fully expect AI to produce a high CVE count next year, I don’t think it will be another “double the number of the previous year”.
Consider two points of view,
Firstly, This years count is mostly “low hanging fruit” with the increase in numbers due to “automation” finding new “instances” of vulnerability in known existing classes of vulnerability in essence by Stochastic methods or in effect “fuzzing”.
Secondly, Future count increases will be dependent on finding new classes of vulnerability, and at the moment that is still a mostly “human activity” not “AI activity”.
I’ve gone through the why of this a couple of times on this blog but the main issue is that fuzzing is an “Acorn” process of “covering the map” of vulnerabilities.
That is “acorns fall under or very close to the parent tree” and thus the wood increases in coverage very slowly and quite densely.
Other plants cast their seeds to the wind thus become widely and distantly scattered and cover ground quickly though quite sparsely.
This is the way knowledge by human intelligence tends to grow.
Thus we can expect “fuzzing” / “AI activity” to grow quickly over a small area then slow down as the ground gets taken up, and things change from “finding in an area” to “finding on the perimeter”.
But “scatter gun” / “Human activity” being in effect “wide area” will continue to grow at a more continuous rate.
Which means that the AI has to be “retrained” very rapidly to take advantage of human insight.
Untill quite recently “retraining an LLM” has been a very expensive process in the order of tens of millions of dollars. A lack of income for the Frontier AI companies will quickly limit the retraining / update cycles for basic economic reasons.
Thus we could have expected an initial burst of activity followed fairly quickly by a significant slow down.
However quite recently we’ve seen new methods of “adjusting LLM weights” that have the potential to make retraining a continuous process at what is a much lower cost.
But what ever the increase of AI ability, we are as the code base is finite, run out of vulnerabilities to find so even the AI vulnerability finding rate will drop.
But don’t hold your breath… Based on the quality of “vibe code” so far Current AI LLM and ML Systems are failing the
“Physician heal thyself”
Test, as the AI produced “vibe-code” has been worse than the human “code-cutter” “sausage machine-code” when it comes to introducing vulnerabilities.
Ismar • November 15, 2026 3:30 AM
&Clive One thing you did not mention is that we can put more effort in forcing AI generated code to follow a tight set of best security practices reducing the new number of vulnerabilities.
I know this isn’t enough to provide highest level of security in a system but it’s a good step in the right direction as the same technology which is used to discover vulnerabilities can be used to prevent them from happening in the first place.
So let’s concentrate on solutions rather than on the problems 😀
Clive Robinson • November 15, 2026 3:55 PM
@ Ismar, ALL,
With regards,
“we can put more effort in forcing AI generated code to follow a tight set of best security practices reducing the new number of vulnerabilities.”
The idea of “vibe-coding” was to,
“Get the LLM to ‘cut the code’ and do the syntax correct typing.”
So a human can,
“Wave the hand to ‘stitch patterns together'”
The problem is that whilst generic patterns may be semi-secure the interfaces and communications between patterns are where the security failings all to frequently occur.
Thus,
“Forcing AI generated code to follow a tight set of best security practices”
Is going to be problematic at best. Because all that has been done is create more complex “kitchen sink” patterns that in effect become a new ill defined “high level language”.
The reason is the problem with “all things to all people” “kitchen sink” patterns is that the generality,
1, Increases complexity in the pattern.
2, Increases edge and corner case usage.
3, Creates functional voids.
4, Dramatically over complicates the interfaces.
Thus the aim of
“Reducing the new number of vulnerabilities.”
Is at best unlikely.
One of the issues we have with “spoken language” is “Double Meanings” giving rise to at best imprecision.
A subset of “spoken language” when translated into the “written form” can be seen as an example is the language used for “Legislation, Regulation, and Standards”.
Where all sorts of issues happen with the likes of commas,
“The comma is a punctuation mark that separates elements within a sentence. It signals a brief pause or a grouping of related items, and it clarifies the structure of a sentence so the reader can follow the meaning without confusion.
There are more than ten distinct uses of the comma in English, from separating items in a list to setting off nonrestrictive clauses, joining independent clauses with a conjunction, and clarifying dates and numbers. Some uses are grammatical requirements; others are style choices that vary between American and British English.
…
“
https://aceenglishgrammar.com/comma/
It also notes the reasons as to why in general the comma is problematical,
“The comma is one of the most-used punctuation marks in English, and it also causes the most confusion. Some uses of the comma are required by grammar rules; others depend on style, dialect, or the writer’s judgment.
Note that the comma is a lighter separator than the period (which ends a sentence) or the semicolon (which joins two related independent clauses). The three marks operate at different levels of sentence structure.“
Thus allows for disparate usage such as in “American English”, and “British English”; with dates, or the “Oxford Comma” or “Serial Comma”.
And the comma, is not the only grammatical cause of problems.
Then there is the likes of “minute” of time, or in size.
And occasionally capitalisation, with, the Polish polish with little circles to the left.
English in its various forms is almost always a “lazy language” with “overloading” being a norm, that is not conducive to clarity.
It’s a problem with Current LLM and ML Systems that is not going to go away. Thus,
“a tight set of best security practices”
Can not be constructed without confusion in either American English, or British English. As for any of the many regional variants, just scream at the clouds 😉
It’s a subject I’ve been mulling over for a while. Because if you think about it “vibe-coding” is a very bad way to move up the computing stack from the “programming language” to the “specification”…
There is a good reason why Cobol was hated by many… It was a cludge in 1960 and still is even in it’s 2023 “stable” version that had Object Orientation added earlier in 2002…
Compare the pre 1960 aims and objectives that gave rise to Cobol and the aims and objectives of LLM based “vibe-coding”…
Then if you feel like it you can,
“Run screaming from the room, pulling out your hair, wailing about the utter futility of getting cheap and easy ways for normal humans to write high quality code.” 😉
Subscribe to comments on this entry
Sidebar photo of Bruce Schneier by Joe MacInnis.
Travis • November 13, 2026 10:56 PM
Where’s the rest of the article