Itdaily - ‘Download and forget is over’: open source community thanks EU for the CRA

‘Download and forget is over’: open source community thanks EU for the CRA

Thierry Carrez Linux Foundation
Thierry Carrez, GM Linux Foundation Europe. Source: Linux Foundation

AI tools are finding more vulnerabilities in open source than maintainers can handle. The Cyber Resilience Act places responsibility on the companies that build open source into their products, and the community welcomes that. 

At the Open Source Summit in Prague, speakers are throwing around dramatic figures on software security. “This year alone, 66,000 CVEs have already been added,” said Jamie Thomas, Chief Client Innovation Officer security at IBM. “Nobody was waiting for that.” Harrison Ripps, Director of Engineering at subsidiary Red Hat, cites an even higher figure: 87,500 CVEs in twelve months. 

Has software suddenly become far less secure? No, but with the help of AI, many more vulnerabilities are being discovered than before. The pressure this puts on software security, and on open source in particular, comes up regularly during the conference. The European Cyber Resilience Act (CRA) is meant to help spread the burden across more shoulders.

Flooded with CVEs 

Thierry Carrez, General Manager of Linux Foundation Europe, talks about an “influx” of contributions to open source projects. He gives OpenStack as an example: “This year the project had 42 security advisories, twenty times more than usual. AI makes contributing to open source easier, but it also brings a flood of bad contributions, or more contributions than the maintainers of the code can handle.” 

In a conversation with ITdaily, Carrez takes a broader view than open source alone. “It is disruptive for all software. In commercial software the problem is even bigger: look at the vulnerabilities that are patched every day. The resources available for open source are no longer enough. All projects feel the pain.” According to Carrez, AI currently helps mainly in the first phase of code development.

Ripps points to the pressure this puts on small projects. “A CVE makes no distinction between large companies and small developers. The latter are coming under more and more pressure to patch vulnerabilities.” The approach has to change, says Thomas. “Speed is the enemy right now: disclosure is faster than patching. As defenders, we have to use AI, but it still causes too much noise. Experienced developers lose time cleaning up AI patches.” 

Carrez is cautiously positive. “AI mainly helps in the early stages of software development right now. The challenge is to push its impact to higher levels. The lower levels will not suddenly be replaced. We are watching the scene as it unfolds.”  

Software in a box 

Besides AI, European legislation is a major topic of conversation at the conference. According to Carrez, the first draft of the Cyber Resilience Act (CRA) showed “no understanding whatsoever” of open source.  

“The legislation initially held contributors responsible for the code they worked on. That could have put people off taking part in projects. You don’t buy software in a box, but that is exactly what the first draft assumed. Fortunately, we were able to explain this to the policymakers.”

Three years ago at KubeCon, we already heard similar concerns from Carrez’s predecessor Gabriele Columbro. In an interview with ITdaily, Columbro said that “the proposed rules could discourage developers from starting new open source projects.” The community argued against being lumped together with commercial software. “Everyone plays a role in security, vendors first and foremost, of course,” said Columbro. 

According to Carrez, the EU has listened to those concerns. The current text of the law, which now applies, distinguishes between three roles: manufacturers, stewards and maintainers. “Whoever puts the product on the market is responsible. This takes much more account of how open source works. We are moving from begging for forgiveness to shared responsibility. There are open channels: we can listen to and learn from each other.” 

You don’t buy software in a box. The CRA initially assumed you did.

Thierry Carrez, General Manager Linux Foundation Europe

Software buffet 

The experts now sound much more positive about the legislation. Madalin Neag, EU Policy Advisor at OpenSSF,  calls the CRA “a very good piece of legislation” without hesitation. “Security is an important layer in the supply chain. Responsibility for it now lies entirely downstream, away from maintainers, unless they maintain commercial solutions.” 

According to Neag, the addition of “stewards” as a new category between manufacturers and maintainers is “very welcome”. Under the CRA, an organisation designated as a steward, such as the Linux Foundation, must have a cybersecurity policy, cooperate with market surveillance authorities and report actively exploited vulnerabilities.  

“Nothing goes beyond the steward layer. Maintainers can no longer keep up with the work. They do a lot on a voluntary basis. Let’s not burden them unnecessarily, so that they can focus on innovation.” 

Christopher Robinson, CTO of OpenSSF and Akrites, sees consumer protection as an important goal of the legislation. “The greatest responsibility lies with the vendor, and rightly so. Software has been developed like an ‘all-you-can-eat buffet’ for too long. There were hardly any rules. Best practices are now laid down.” 

Since 11 September, manufacturers have had to report actively exploited vulnerabilities within 24 hours. The law applies in full from December 2027. There is still quite some work to do, as shown by a survey by the Linux Foundation in June: 66 percent of 843 organisations surveyed admitted they do not know the CRA, and only a minority expects to be ready by the deadline. Awareness is lowest outside Europe, even though the legislation applies to all companies that want to bring their products to the European market.  

“The CRA does not stop at the text. Other countries and regions want to follow Europe’s example. Companies need to understand whether they are compliant,” says Neag.  

NIS2 and DORA ask for the same 

Neag acknowledges that these are complex times for software companies. The CRA is just one of many laws with an impact. According to him, companies that also fall under NIS2 or DORA receive different questionnaires about their supply chain.  

“The laws share the same core: securing the supply chain, identifying the role of open source in it and encouraging downstream responsibility. Policymakers are getting closer to open source and understand its importance in critical infrastructure. But you can’t secure thousands of components with a piece of paper. Then you have to go knocking on hundreds of doors.” 

“The first thing you can do is make your products secure,” says Neag. He advises looking at the laws together and finding the overlap, such as risk management. “Otherwise you get confused. NIS2 is also a directive, to which each member state can add its own rules.” In Belgium, that happened with the NIS2 law, which is supervised by the Centre for Cybersecurity Belgium (CCB). 

You can’t secure thousands of software components with a piece of paper.

Madalin Neag, EU Policy Advisor OpenSSF

‘Patchmageddon’ 

The open source world is putting its heads together to deal with this new reality and complexity. OpenSSF uses health scores to track down structural risks in projects, while Akrites helps maintainers with an incident response team so that those problems are also fixed quickly. The initiative launched on 25 June, with Ericsson and Vodafone among its founding members. 

According to Neag, Akrites was set up to deal with “AI slop”, although its role is broader. He also refers to the action plan for cybersecurity and AI that the European Commission presented on 7 July. In it, ENISA maps critical open source components for a campaign meant to speed up patching. “Human review remains necessary to develop secure code,” says Neag.  

Gabriele Columbro is attending this year as Executive Director of FINOS, an open source foundation for the financial sector. According to Columbro, we are experiencing a true “Patchmageddon” today, referring to a paper by J.P. Morgan. The paper’s conclusion: patching is slowing down, while attackers are exploiting vulnerabilities faster with the help of AI.  

“Patching is going from an acceptable risk to a top priority. In the financial sector, this involves much more than just snapping your fingers. Banks must be able to prove what they patch. The IT budget largely goes to ‘keeping the lights on’. Often, people pay several times for the same patch,” Columbro observes. 

Download and forget is over

In times of need, new friendships are formed. Commercial vendors are keen to show that open source is close to their heart. “Putting obstacles in the way of open source is bad for security,” says Mark Weatherford, Head of Cybersecurity Policy at Nvidia. “It is important that researchers and professionals come together around guardrails for AI and the analysis of incidents. Not to punish, but to learn from them.”

“You can no longer bring open source software to market without communicating with the community,” says Carrez. According to him, it will take a while before all manufacturers adapt. “We believe it will ultimately lead to healthier relationships between all links in the chain.” 

“Downloading code and then forgetting about it, that stops now,” says Neag. He calls on companies to contribute actively to open source projects, either through funding or through active participation. “Collaboration runs in two directions: upstream to report on vulnerabilities and downstream to fix them. Nobody can defend the supply chain alone,” he concludes.