Connect with us

CyberSecurity

NIST Drops NVD Enrichment for Pre-March 2026 Vulnerabilities: What It Means for Cybersecurity

Published

on

NIST Drops NVD Enrichment for Pre-March 2026 Vulnerabilities: What It Means for Cybersecurity

The NVD enrichment process is undergoing a major overhaul. The US National Institute of Standards and Technology (NIST) has announced it will stop enriching most vulnerabilities reported before March 1, 2026, in a bid to manage an unprecedented surge in CVE submissions. This shift to a risk-based approach aims to focus resources on the most critical threats, leaving many older vulnerabilities unanalyzed.

Speaking at VulnCon26 in Scottsdale, Arizona, on April 15, Harold Booth, a NIST computer scientist, explained the reasoning behind the change. “CVE reporting keeps increasing – and trust me, at the NVD, we see them all – and our ability to keep up is just not there, so our backlog keeps increasing too,” he said.

Why NVD Enrichment Is Being Rethought

The decision stems from a dramatic rise in reported vulnerabilities. According to a NIST statement published on April 15, CVE submissions jumped by 263% between 2020 and 2025. In 2025 alone, the NVD enriched nearly 42,000 CVEs – 45% more than any prior year. Yet, the backlog continues to grow.

“Submissions during the first three months of 2026 are nearly one-third higher than the same period last year,” Booth noted. “We’ve been trying to develop new tools to help with this, but with our current methods, I will admit this is just something we can’t keep up with.” This trend is expected to accelerate, with the Forum of Incident Response and Security Teams (FIRST) forecasting a record-breaking 50,000 additional CVEs in 2026.

Jerry Gamblin, principal engineer at Cisco Threat Detection & Response, predicts an even higher figure: 70,135 CVEs by year-end, representing a 45.6% growth rate over 2025. These forecasts do not account for new generative AI models from Anthropic and OpenAI, such as Claude Mythos and GPT-5.4-Cyber, which promise to autonomously find and fix vulnerabilities at scale.

How the New Risk-Based Approach Works

Under the revised framework, the NVD will prioritize vulnerabilities that pose the greatest threat. Specifically, enrichment will focus on:

  • Software used by the US federal government
  • Critical software as defined by Executive Order 14028 (2021)
  • Vulnerabilities on the CISA Known Exploited Vulnerabilities (KEV) list

“All submitted CVEs will still be added to the NVD. However, those that do not meet the criteria above will be categorized as ‘Not Scheduled,’” Booth explained. This means that thousands of older, less critical vulnerabilities will remain unenriched indefinitely.

Booth emphasized the rationale: “Vulnerabilities are a way for an attacker to gain access to a system that they should not and we want to close those holes as quickly, efficiently and effectively as possible. We want to focus on the ones that are important, not the ones that are unimportant.” Users can still request enrichment of unscheduled CVEs by emailing the NVD at nvd@nist.gov.

Changes to CVE Scoring and Analysis

Alongside the prioritization shift, the NVD has updated its scoring and analysis procedures. It will no longer provide its own CVSS severity scores for CVEs already scored by the submitting authority, unless the score appears inaccurate. Additionally, the NVD will only reanalyze modified CVEs if changes materially impact enrichment data.

To improve clarity, status labels have been revised. The previous ‘Deferred’ status is replaced with ‘Not scheduled,’ indicating that the NVD will not enrich the corresponding CVE. A new document explaining these labels is now available on the NVD website.

Implications for Vulnerability Management

This shift in NVD enrichment policy has significant implications for cybersecurity teams. Organizations can no longer rely on the NVD to analyze every vulnerability. Instead, they must adopt a more proactive approach, leveraging threat intelligence feeds and internal risk assessments.

For example, vulnerability management best practices now require prioritization based on exploitability and business impact. Tools like the CISA KEV list provide a starting point, but teams must also consider their unique threat landscape. Integrating the CISA KEV list into your workflow can help identify actively exploited vulnerabilities.

Furthermore, the rise of AI-driven vulnerability discovery tools means the volume of CVEs will only increase. AI-powered cybersecurity tools are changing the game, but they also create new challenges for databases like the NVD.

What Comes Next for the NVD

NIST acknowledges that these changes are temporary measures. Booth noted that the team is developing new tools to handle the workload, but admits that current methods are insufficient. The agency is also exploring partnerships with industry and academia to improve efficiency.

For now, the focus is on reducing the backlog and ensuring that critical vulnerabilities receive timely attention. As Booth stated, “We want to close those holes as quickly, efficiently and effectively as possible.” The cybersecurity community will be watching closely to see if this risk-based approach delivers on its promise.

CyberSecurity

Paragon Refuses to Cooperate With Italian Authorities in Spyware Probe, Report Alleges

Published

on

Paragon Refuses to Cooperate With Italian Authorities in Spyware Probe, Report Alleges

New allegations suggest that Paragon Solutions, the Israeli-American surveillance technology firm, is stonewalling Italian prosecutors investigating a massive spyware scandal. According to a report from Wired Italy, the company has failed to respond to a formal request for information sent via the Israeli government—more than a year after the investigation began. This development marks a significant turn in the ongoing Paragon spyware scandal, which has shaken Italy’s political and journalistic communities.

Last year, both WhatsApp and Apple alerted several Italian citizens—including journalists and activists—that they had been targeted with government-grade spyware. WhatsApp specifically identified Paragon as the supplier of the “Graphite” spyware used in a global hacking campaign that affected roughly 90 individuals. The notifications triggered a wave of criminal complaints and a formal investigation by Italian prosecutors.

The Alleged Refusal to Cooperate in the Italian Spyware Investigation

Building on the initial scandal, the latest twist involves Paragon’s apparent unwillingness to assist authorities. Wired Italy reports that prosecutors in Rome and Naples jointly sent a formal request for information to Paragon through diplomatic channels. However, the company has not replied. This silence contradicts earlier public statements from Paragon, in which the firm claimed it had offered to help investigate the hacking of a journalist—an offer it says the Italian government rejected.

As a result, Paragon even canceled its contracts with Italy’s two main intelligence agencies, AISE and AISI. The company argued that the Italian government turned down its proposal to probe whether a journalist was actually spied on using Graphite. This public feud between a spyware vendor and a former client is highly unusual in the secretive surveillance industry.

Possible Reasons for Paragon’s Silence

Observers speculate that the Israeli government may have intervened to block Paragon’s cooperation. In 2024, The Guardian reported that Israeli authorities seized documents from NSO Group to prevent the company from complying with legal demands in a lawsuit brought by WhatsApp. Israeli human rights lawyer Eitay Mack told Wired Italy that while the Israeli government has the legal power to force local companies to cooperate with foreign judicial requests, it has never done so. This context raises questions about whether Paragon is acting on its own or under state pressure.

Meanwhile, Spain’s High Court closed its own investigation into NSO spyware targeting Spanish politicians earlier this year, citing a lack of cooperation from Israeli authorities. This pattern suggests a broader reluctance among Israeli surveillance firms to engage with foreign probes.

Paragon’s Attempt to Position Itself as an Ethical Alternative

In the history of government spyware, it is extremely rare for a company to engage in a public dispute with a former customer. Paragon’s aggressive stance appears to be part of a strategic effort to differentiate itself from rivals like NSO Group and Intellexa, which have been mired in numerous scandals worldwide. The company’s now-defunct official website once claimed it provides customers “with ethically based tools, teams, and insights.”

However, the Paragon spyware scandal is its first major public controversy. The firm currently holds an active contract with U.S. Immigration and Customs Enforcement (ICE), which has been using Paragon’s technology to arrest and deport tens of thousands of immigrants. ICE told lawmakers that its law enforcement arm, Homeland Security Investigations (HSI), deploys Paragon’s spyware to counter terrorism and drug trafficking.

Italy’s Government Denies Involvement in Journalist Hacking

Italy’s government, led by Prime Minister Giorgia Meloni, has consistently denied authorizing the hacking of journalists Francesco Cancellato and Ciro Pellegrino, both of whom work for the online news outlet Fanpage. The Citizen Lab, a leading research organization that has investigated spyware abuses for over a decade, confirmed that both journalists were compromised using Graphite. Other victims include activists from Mediterranea Saving Humans, an Italian nonprofit dedicated to rescuing migrants crossing the Mediterranean Sea.

In June of last year, the Italian parliamentary committee overseeing intelligence agencies concluded that the targeting of activists was lawful. However, the committee stated it could not find evidence that Cancellato was targeted, and it did not examine Pellegrino’s case at all. Then, in March, the same prosecutors who requested information from Paragon announced that a forensic analysis of Cancellato’s device confirmed he was hacked, though the results for Pellegrino’s phone were inconclusive.

What Comes Next for the Italian Spyware Probe?

The prosecutors’ investigation remains open. Without Paragon’s cooperation, Italian authorities face significant hurdles in uncovering the full scope of the spyware campaign. This situation underscores the challenges that national governments encounter when trying to hold foreign surveillance companies accountable. For now, the Paragon spyware scandal continues to unfold, leaving journalists, activists, and legal experts watching closely for any signs of progress—or further obstruction.

For more insights into similar cases, read about how spyware targets journalists globally and explore the ethics of government surveillance.

Do you have more information about Paragon Solutions and the spyware scandal in Italy? Contact Lorenzo Franceschi-Bicchierai securely on Signal at +1 917 257 1382, or via Telegram and Keybase @lorenzofb, or email.

Continue Reading

CyberSecurity

Cookeville Regional Medical Center Discloses Rhysida Ransomware Attack Affecting 337,917 Patients

Published

on

Cookeville Regional Medical Center Discloses Rhysida Ransomware Attack Affecting 337,917 Patients

A major Rhysida ransomware breach has hit Cookeville Regional Medical Center (CRMC) in Tennessee, exposing the personal and medical data of 337,917 individuals. The hospital confirmed the incident this week, sending breach notification letters to affected patients nearly nine months after the attack was first detected.

This healthcare ransomware attack, which occurred in July 2025, ranks among the largest in the United States for that year. The 309-bed facility serves about 250,000 patients annually across 14 counties in the Upper Cumberland region, making the scale of the data compromise particularly concerning for the local community.

How the Rhysida Ransomware Breach Unfolded at CRMC

According to a filing with the Maine Attorney General’s Office, an unauthorized party accessed or acquired files between July 11 and July 14, 2025. The Rhysida ransomware group, a Russia-linked ransomware-as-a-service operation active since May 2023, claimed responsibility on August 2, 2025. The gang demanded a ransom of 10 Bitcoin—worth roughly $1.15 million at the time—and posted sample files on its dark web leak site. It remains unclear whether any ransom was paid.

The hospital began mailing notification letters on April 14, 2026, roughly nine months after the intrusion. This delay, while typical for complex investigations, left patients in a prolonged state of uncertainty about their data security.

Data Exposed in the Attack

The compromised information may include names, addresses, dates of birth, Social Security numbers, driver’s license numbers, financial account details, medical record numbers, treatment information, and health insurance data. CRMC is offering 12 months of free identity theft protection through Experian to those affected.

Given the sensitive nature of medical records, this Rhysida ransomware breach poses significant risks for identity theft and medical fraud. Patients are advised to monitor their accounts closely and take advantage of the offered protection services.

The Growing Threat of Rhysida Ransomware in Healthcare

The CRMC incident is not an isolated case. According to Comparitech, which tracks healthcare breaches, this ranks as the eighth-largest US healthcare ransomware breach of 2025 by records compromised. Last year, there were 134 confirmed attacks on US healthcare providers, exposing 11.7 million records in total.

Rhysida alone claimed 91 attacks across all sectors in 2025, with 23 confirmed. The average ransom demand from the group was $1.2 million. Other recent healthcare victims of Rhysida include Florida Lung, Asthma & Sleep Specialists (May 2025, $639,000 demand), MedStar Health in Maryland (September 2025, $3.09 million demand), and Spindletop Center in Texas (September 2025, $1.65 million demand).

These incidents highlight the persistent targeting of the healthcare sector by ransomware groups. For more on Rhysida’s tactics, see our analysis on Rhysida Ransomware Analysis Reveals Vice Society Connection.

Why Breach Notifications Take So Long

Rebecca Moody, head of data research at Comparitech, explained that the lengthy investigation timeline reflects the scale of forensic work required after a hospital ransomware hit. “It can take a considerable amount of time for organizations to investigate what data has been impacted in these breaches,” she said.

“While some organizations avoid using the word ‘ransomware’ and don’t issue any form of data breach notification for months,” Moody added, “this lack of clarity and confirmation can leave those affected open to identity theft and phishing campaigns.” CRMC, however, has been transparent about the nature of the attack, which helps patients understand the risks they face.

Impact on Patient Care and Hospital Operations

Ransomware incidents at US hospitals routinely force extended downtime, canceled appointments, and patient diversions, even when clinical systems remain operational. In CRMC’s case, the hospital stated it has put additional security measures in place since the attack to prevent future incidents.

For patients, the immediate concern is the potential misuse of their data. Social Security numbers and medical records are particularly valuable on the black market, often fetching higher prices than credit card numbers. This means that even if no direct financial loss occurs, victims may face long-term risks such as fraudulent medical claims or identity theft.

Healthcare organizations across the country are increasingly investing in cybersecurity defenses, but as the CRMC case shows, the threat from groups like Rhysida remains potent. For more insights on protecting patient data, read our guide on Healthcare Cybersecurity Best Practices.

In conclusion, the Rhysida ransomware breach at Cookeville Regional Medical Center underscores the urgent need for robust cybersecurity in healthcare. With 337,917 patients affected and sensitive data exposed, this incident serves as a stark reminder of the vulnerabilities in our medical infrastructure. Patients are urged to remain vigilant and take advantage of identity protection services offered by the hospital.

Continue Reading

CyberSecurity

APK Malformation Found in Thousands of Android Malware Samples: A New Evasion Frontier

Published

on

APK Malformation: How Attackers Are Bypassing Android Security Checks

When it comes to APK malformation, the numbers are staggering. Researchers from Cleafy’s Threat Intelligence and Incident Response team have identified this evasion technique in over 3,000 malicious Android samples. Families like Teabot, TrickMo, Godfather, and SpyNote are all leveraging broken APK structures to slip past static analysis tools.

At its core, APK malformation is a deliberate act: attackers craft non-standard or corrupted Android Package files that still install and run on devices. The trick lies in the Android installer’s leniency. It tolerates inconsistencies that strict parsers cannot, allowing malicious apps to function normally while frustrating reverse engineering efforts.

How APK Malformation Bypasses Static Analysis

An APK is essentially a ZIP archive containing code, resources, and a manifest. Each file sits behind a Local File Header, and a Central Directory acts as a table of contents. Attackers introduce conflicts between these structures. Tools like JADX crash on the inconsistency, but the Android installer quietly proceeds.

Cleafy’s team catalogued several active techniques:

  • Directory-file name collisions that confuse parsers about which entry to load
  • Unsupported compression methods that Android treats as uncompressed, but analysis tools fail on
  • False password protection flags placed inconsistently across headers
  • Mismatched checksums, file sizes, and offset references between header structures
  • AndroidManifest.xml corruption through magic header changes, string pool manipulation, and malicious offset injection

Another method abuses the assets/directory by storing payloads under filenames with non-ASCII or control characters. This triggers path traversal errors during decompilation, forcing analysts to manually extract and inspect archive contents.

Defenders Push Back With Open-Source Tooling

In response, Cleafy released Malfixer, a Python utility that detects and repairs malformed APKs. It rebuilds them into a form conventional reverse engineering tools can parse. The project, published on GitHub, was developed after analyzing more than 70 malformed samples from the TrickMo, Teabot, Godfather, and SpyNote families.

This release reflects a wider arms race. Cleafy noted that earlier incidents failed to classify samples later linked to TrickMo precisely because malformation techniques prevented standard static analysis. “As defenders, we must evolve our tools and techniques to counter these evasive tactics,” the researchers wrote, urging the community to contribute new samples and methods.

Practical Implications for Android Security

For security teams, this means that static analysis alone is no longer sufficient. Combining it with dynamic analysis and behavior monitoring is essential. Organizations should also consider integrating tools like Malfixer into their malware analysis pipelines to catch malformed APKs early.

As malware authors refine their techniques, defenders must keep pace. The battle over APK malformation is just one front in a larger war for mobile security. Staying informed and updating toolkits is critical.

For more on Android malware evasion, check out our guide on Android Malware Evasion Techniques and learn about Static Analysis Limitations.

Continue Reading

Trending