aifollow.news Search
Back IT之家 科技新闻
IT之家 科技新闻· · Original publication time AI score40

CVE Tracker shows a sharp rise in vulnerability reports in 2026Machine translation

CVE Tracker 显示 2026 年漏洞报告数量陡增

Automatically verified and published · Generated and evidence-checked automatically; not reviewed by a human.

AI-assisted summary

Developer @0x_Osprey’s CVE Tracker charts vulnerabilities assigned CVE identifiers and shows release dates for major AI models. The report notes that pre-release model testing may also be used to find vulnerabilities, so release dates need not align with changes in report volume. More reports do not necessarily mean systems have become more dangerous.

Article · AI translation

IT Home reported on October 28 that technology outlet Gigazine published a post today (October 28) saying that developer @0x_Osprey created the CVE Tracker website. Using visual charts, it tracks changes in the number of vulnerabilities assigned CVE (Common Vulnerabilities and Exposures) identifiers, clearly showing a steep rise in vulnerability reports since the start of 2026.

IT Home notes: CVE is a vulnerability identification system widely used worldwide. Security researchers, software vendors and businesses commonly use it to track, fix and disclose security flaws. CVE Tracker organizes these public records into trend charts. Users can also view the release dates of major AI models to examine their relationship with peaks in vulnerability discoveries.

The report points out that AI companies often use test versions to find and report vulnerabilities before formally releasing their models, so model launch dates do not necessarily coincide exactly with sharp increases in vulnerability counts.

The outlet said AI is becoming an “amplifier” for security research: it can scan code, reproduce anomalous behavior and compile reports more quickly, bringing parts of software that would be difficult for people to cover into the scope of inspection.

But the discovery of “more vulnerabilities” does not necessarily mean systems have “become more dangerous.” More reports may expose real risks, but they may also include low-quality, duplicate or hard-to-verify vulnerability reports, increasing the triage burden on open-source maintainers and security teams.

Found an error? Send a correction