KEVWire / Security intelligence

Intelligence brief

The intelligence wire

8316 matching records

AI systems acting on their own. AI used by attackers. Flaws in and attacks on AI systems. Defensive research.

A chronological reading list. Attribution stays qualified: an affected AI product is not evidence of an AI-assisted attack, and an AI system's own action is not an outside attack. Scope is only as broad as the source states.

Context: measured KEV catalog additions

Counts of records in the last complete validated CISA KEV catalog, grouped by each source dateAdded month (UTC calendar month). The denominator is the disclosed current catalog, not the editorial sample. This measures catalog additions represented in that snapshot, not worldwide attacks, discovery dates, zero-days, or causation by AI; removals can change historical counts.

Catalog snapshot: Oct 23, 2026. 1756 catalog records.

CISA KEV catalog additions by month; not worldwide attacks
Month	Additions
2021-11	291
2021-12	20
2022-01	40
2022-02	32
2022-03	226
2022-04	45
2022-05	83
2022-06	48
2022-07	3
2022-08	23
2022-09	24
2022-10	12
2022-11	10
2022-12	9
2023-01	5
2023-02	14
2023-03	18
2023-04	17
2023-05	19
2023-06	24
2023-07	16
2023-08	8
2023-09	19
2023-10	18
2023-11	18
2023-12	11
2024-01	21
2024-02	9
2024-03	10
2024-04	10
2024-05	14
2024-06	9
2024-07	14
2024-08	19
2024-09	25
2024-10	17
2024-11	22
2024-12	16
2025-01	14
2025-02	27
2025-03	32
2025-04	15
2025-05	24
2025-06	20
2025-07	20
2025-08	15
2025-09	16
2025-10	31
2025-11	11
2025-12	20
2026-01	17
2026-02	28
2026-03	26
2026-04	31
2026-05	21
2026-06	23
2026-07	26
2026-08	31
2026-09	43
2026-10	26

RSS JSON CSV

Missing records are not an all-clear. Read the coverage and methodology.

Sources & methods

23 current, 2 cached; each source has a bounded scope.

Editorial Evidence Review

editorial · 19 retained records

Selective historical baseline reviewed on 2026-10-26, not complete or live worldwide monitoring. Dates describe cited disclosures, not necessarily incident occurrence. Known exploitation does not establish continuing attacks today, zero-day use, or attacker AI use. This sample is not a denominator for global or AI incident trends.

A manually reviewed, dated editorial sample, not a live feed. Source claims and dates remain tied to each record; no invented scores or trends.

Last successful retrieval: Not yet recorded.

CISA Known Exploited Vulnerabilities

live · 1756 retained records

The full successfully validated KEV catalog, without a newest-record slice.

Known exploitation is not necessarily a zero-day. KEV-only publication dates denote catalog additions, not initial disclosure. Due dates concern covered US federal agencies, not your SLA. The last complete catalog is retained for 30 days; oversized or incomplete replacements are rejected, not truncated.

Last successful retrieval: Oct 26, 2026, 21:40 UTC.

Source documentation

GitHub Public Security Advisories

cached · 314 retained records

GitHub-reviewed public advisories, sorted by update date; at most 3 cursor pages of 100 records per cycle, without authentication.

Not the entire advisory database. GitHub review is upstream review, not local editorial review or proof of remediation. Withdrawn advisories are excluded. Retained union is bounded to 2,000 records updated within 180 days; public API rate limits can reduce coverage.

Last successful retrieval: Oct 26, 2026, 20:56 UTC.

Public source returned an error. (HTTP 429)

Source documentation

JPCERT/CC Japan Advisories

live · 32 retained records

Current Japanese-language alerts and weekly report entries, with the exact article or weekly-report anchor.

RSS usually supplies only a Japanese title and date. Titles matching JPCERT/CC's fixed patterns are shown in English via a deterministic glossary translation with the original Japanese retained; unmatched titles stay in Japanese rather than being guessed. No affected-version detail is invented. Japan denotes this advisory audience, not a scan or proof of exposure. Up to 500 records are retained for 365 days.

Last successful retrieval: Oct 26, 2026, 21:40 UTC.

Source documentation

Google Project Zero Research

live · 10 retained records

Security-research entries in the official Atom feed, including explicit AI-defense research when present; no archive crawling.

The official feed is large but contains a bounded current entry list. Excerpts are not full articles. Ordinary fuzzing, automation, and exploit research are not classified as AI. Up to 250 records are retained for 730 days.

Last successful retrieval: Oct 26, 2026, 21:35 UTC.

Source documentation

Google Security Research

live · 47 retained records

At most the 50 entries supplied by the official Google Security RSS endpoint; security-topic filtering and conservative, source-linked AI classifications.

Not all Google research or all AI defense. Product security and prompt-injection research do not establish attacker AI use. Excerpts are not independently reproduced findings. Up to 250 records are retained for 730 days.

Last successful retrieval: Oct 26, 2026, 21:35 UTC.

Source documentation

NVD Recently Published CVEs

live · 6000 retained records

Every CVE in the NVD, from any vendor worldwide, that any scorer (the vendor/CNA, NVD, or CISA) rates HIGH or CRITICAL, or that CISA's assessment reports as actively exploited. A 14-day backfill on first run, then every CVE modified since the last successful retrieval.

Medium and low severity CVEs are not ingested; unscored CVEs appear once scored. The CNA (vendor) score is preferred over NVD's own when both exist. NVD publication is not evidence of exploitation. Up to 6,000 records are retained for 120 days.

Last successful retrieval: Oct 26, 2026, 21:37 UTC.

Source documentation

BleepingComputer Security Reporting

unavailable · 0 retained records

Breach, vulnerability, and exploitation reporting selected from the current syndication feed, with exact article links.

Reporting, not independently primary-confirmed or locally reviewed. A record is marked as known exploitation only when the headline or excerpt explicitly reports exploitation. Headline filtering is not a complete census. No fabricated scores, losses, CVEs, or AI attribution. Retained for 90 days.

Last successful retrieval: Not yet recorded.

Public source returned an error. (HTTP 403)

Source documentation

The Hacker News

live · 30 retained records

Breach, vulnerability, and exploitation reporting selected from the current syndication feed, with exact article links.

Last successful retrieval: Oct 26, 2026, 21:40 UTC.

Source documentation

SecurityWeek

live · 6 retained records

Breach, vulnerability, and exploitation reporting selected from the current syndication feed, with exact article links.

Last successful retrieval: Oct 26, 2026, 21:35 UTC.

Source documentation

Help Net Security

live · 1 retained records

Breach, vulnerability, and exploitation reporting selected from the current syndication feed, with exact article links.

Last successful retrieval: Oct 26, 2026, 21:40 UTC.

Source documentation

The Record (Recorded Future News)

cached · 1 retained records

Breach, vulnerability, and exploitation reporting selected from the current syndication feed, with exact article links.

Last successful retrieval: Oct 26, 2026, 14:15 UTC.

Syndication returned no eligible validated records; HTTP success was not ingestion success.

Source documentation

Axios

live · 3 retained records

General technology and business news, filtered to security stories and incidents involving AI systems; everything else in the feed is skipped.

Last successful retrieval: Oct 26, 2026, 21:35 UTC.

Source documentation

TechCrunch Security

live · 3 retained records

General technology and business news, filtered to security stories and incidents involving AI systems; everything else in the feed is skipped.

Last successful retrieval: Oct 26, 2026, 21:35 UTC.

Source documentation

WIRED Security

live · 5 retained records

General technology and business news, filtered to security stories and incidents involving AI systems; everything else in the feed is skipped.

Last successful retrieval: Oct 26, 2026, 21:35 UTC.

Source documentation

The Verge (AI)

live · 0 retained records

General technology and business news, filtered to security stories and incidents involving AI systems; everything else in the feed is skipped.

Last successful retrieval: Oct 26, 2026, 21:35 UTC.

Source documentation

404 Media

live · 0 retained records

General technology and business news, filtered to security stories and incidents involving AI systems; everything else in the feed is skipped.

Last successful retrieval: Oct 26, 2026, 21:35 UTC.

Source documentation

Have I Been Pwned

live · 121 retained records

Breaches loaded into Have I Been Pwned in the last year: breached organization, account count, exposed data types, breach and load dates, and the organization's disclosure when HIBP links one.

HIBP covers breaches whose data it obtained and loaded; many breaches never appear there. Counts are accounts in the loaded data, not necessarily people. Unverified breaches are labeled as such; fabricated, spam-list, retired, and sensitive breaches are skipped. Up to 400 records are retained for 365 days.

Last successful retrieval: Oct 26, 2026, 21:25 UTC.

Source documentation

DataBreaches.net

live · 5 retained records

Breach and incident reporting selected from the current syndication feed, with exact article links.

Last successful retrieval: Oct 26, 2026, 21:40 UTC.

Source documentation

The HIPAA Journal

live · 8 retained records

Healthcare breach and security reporting selected from the current feed; compliance guides and opinion are skipped.

Last successful retrieval: Oct 26, 2026, 21:25 UTC.

Source documentation

Anthropic

live · 1 retained records

Anthropic news posts about misuse, threats, safety, and security, found through its sitemap (it publishes no feed); at most 8 new pages are read per run.

The company's own disclosure about its systems or threats it observed: authoritative for what the company says, not independent verification. Only posts about misuse, threats, safety, or security are kept. Retained for 730 days.

Last successful retrieval: Oct 26, 2026, 21:26 UTC.

Source documentation

OpenAI

live · 61 retained records

OpenAI news posts about misuse, threats, safety, and security; product and business posts are skipped.

Last successful retrieval: Oct 26, 2026, 21:25 UTC.

Source documentation

Google DeepMind

live · 1 retained records

Google DeepMind blog posts about misuse, threats, safety, and security; product and research-only posts are skipped.

Last successful retrieval: Oct 26, 2026, 21:25 UTC.

Source documentation

Microsoft Security blog

live · 4 retained records

Microsoft Threat Intelligence and security posts: vulnerabilities, threat actors, and AI misuse it observed.

The publishing company's own reporting about threats it observed; not independently confirmed here. Marketing posts are skipped. Up to 300 records are retained for 365 days.

Last successful retrieval: Oct 26, 2026, 21:20 UTC.

1 malformed upstream records were excluded.

Source documentation

AI Incident Database

live · 49 retained records

Reports newly added to the AI Incident Database (Responsible AI Collaborative) that concern security or misuse (deepfakes, scams, influence operations, attacks on or by AI, unauthorized actions), each linking to the original report on its publisher's site. Vehicle crashes, lawsuits, bias, errors, and other non-security harms are skipped; non-English reports usually are too, because the filter reads English.

Inclusion in the database means an editor judged it an AI incident; it is not an independent investigation. The linked report is the evidence. An AI role is assigned only when the report title states it. Up to 500 records are retained for 365 days.

Last successful retrieval: Oct 26, 2026, 20:51 UTC.

Source documentation

FIRST EPSS

live · 7750 retained records

Measured EPSS rows for real CVE identifiers already in this corpus; batches of at most 80 identifiers and under 1,900 CVE-query characters.

Daily model scores estimate exploitation in the following 30 days, not organizational exposure. Missing CVEs receive no default score. Exact scoring dates and per-CVE/date API evidence are retained for 30 days; scores older than 2 days are stale even if a retrieval succeeds.

Last successful retrieval: Oct 26, 2026, 19:41 UTC.

Source documentation

CVE Program CVSS Enrichment

live · 217 retained records

At most 8 published per-CVE documents per cycle, one request at a time, for missing CVSS or an editorial CVE-API measurement not yet rechecked; no NVD polling.

Targeted enrichment, not full CVE coverage. CNA CVSS is preferred; if absent, an explicitly labeled public ADP assessment can supply the actual metric and authoritative source update date. A document with no usable CVSS is not a metric-ingestion success. Unscored targets are deferred for 24 hours. Up to 4,000 enrichments are retained for 30 days.

Last successful retrieval: Oct 26, 2026, 21:31 UTC.

1 targeted CNA requests failed. Public source returned an error. (HTTP 404)

Source documentation

How to read the wire

Context is part of the record.

A bounded source corpus

Data feeds are polled periodically. A successful HTTP request is not, on its own, a successful ingestion. Each source reports its accepted records, scope, and retrieval state.

Editorial selections and reporting are separate from live feeds. Editorial describes how a record was assembled, not whether every claim is independently confirmed.

Evidence before attribution

Primary documents and reporting are labeled separately. AI classifications need an exact supporting source. Reported attribution remains reported; not assessed does not mean ruled out.

An AI-stack flaw is an issue in an AI product. It does not establish attacker AI use or global AI-driven causation.

Measurements, not invented urgency

CVSS is base severity. EPSS is a dated model estimate of CVE exploitation in the following 30 days. Missing measurements stay unavailable, and incident or research records are not scored CVEs.

KEV means known exploitation, not necessarily a zero-day. CISA deadlines apply to covered US federal agencies, not the reader's SLA.

What this does not assess

No scanning, verified exposure, complete asset inventory, or remediation certification. Stack matches use explicit technology tags. Local review marks only record that you chose to review an item.

This source corpus is not worldwide incident frequency. Unknown publication dates and AI involvement remain unknown.

What source statuses mean

Current (live): Usable, validated records were ingested within the source's documented freshness window. Not instantaneous monitoring.
Cached: A previous successful retrieval is retained. Check its date and the source's limitations.
Unavailable: The source could not provide a usable current retrieval. Any retained records are not a current feed.
Editorial: A curated reference or reporting source, not a continuously ingested feed.
Pending: A successful usable ingestion has not yet been recorded.

Measured trend methodology

Catalog snapshot: Oct 23, 2026. 1756 catalog records.

CISA KEV catalog additions by month; not worldwide attacks
Month	Additions
2021-11	291
2021-12	20
2022-01	40
2022-02	32
2022-03	226
2022-04	45
2022-05	83
2022-06	48
2022-07	3
2022-08	23
2022-09	24
2022-10	12
2022-11	10
2022-12	9
2023-01	5
2023-02	14
2023-03	18
2023-04	17
2023-05	19
2023-06	24
2023-07	16
2023-08	8
2023-09	19
2023-10	18
2023-11	18
2023-12	11
2024-01	21
2024-02	9
2024-03	10
2024-04	10
2024-05	14
2024-06	9
2024-07	14
2024-08	19
2024-09	25
2024-10	17
2024-11	22
2024-12	16
2025-01	14
2025-02	27
2025-03	32
2025-04	15
2025-05	24
2025-06	20
2025-07	20
2025-08	15
2025-09	16
2025-10	31
2025-11	11
2025-12	20
2026-01	17
2026-02	28
2026-03	26
2026-04	31
2026-05	21
2026-06	23
2026-07	26
2026-08	31
2026-09	43
2026-10	26

Built to be read by software, too

For AI agents and developers

Everything on this site is available to agents and scripts, read-only and without a key. Records keep their exact source URLs and measurement dates, so an agent can cite the evidence rather than this site.

MCP server: /mcp
Streamable HTTP, stateless. Tools: search_vulnerabilities, get_record, recent_exploited, list_technologies, list_sources.
REST API: OpenAPI 3.1 description; start with /api/intel (the same filters as this page) and /api/sources.
For language models: llms.txt (summary) and llms-full.txt (every retained record).
Feeds: RSS, JSON, and CSV follow every filter, including your stack and hidden sources.

Add KEVWire to an MCP client (Claude, ChatGPT, Cursor, VS Code, and others) with:

{"mcpServers": {"kevwire": {"type": "http", "url": "/mcp"}}}

Please describe coverage honestly: this is a bounded source corpus, not every attack. Known exploitation and CISA KEV membership are different facts, and federal due dates are not an organization's SLA.

Use the underlying data.

Feeds and exports follow the current filters. Exported review IDs are user-supplied reading marks, not verified remediation.

Filtered RSS Filtered JSON Filtered CSV Intelligence API Record schema Source status JSON Measured trend JSON

Back to the wire

Permalink

VulnerabilityCVE-2026-99013

Linux kernel: Bluetooth: ISO: Reject concurrent BIS listener setup

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Reject concurrent BIS listener setup iso_sock_listen() drops the socket lock before calling iso_listen_bis() to preserve the hdev->lock ordering.

Published Oct 23, 2026Updated Oct 24, 2026

Exploited: Not known
Severity: 7.8 High (CVSS 3.1)
Chance of exploitation: 0.2% in the next 30 days
Sources: 1 source

What to do

Check the vendor advisory for affected versions and fixes.

Read NVD CVE-2026-99013

What happened

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: ISO: Reject concurrent BIS listener setup

iso_sock_listen() drops the socket lock before calling iso_listen_bis() to preserve the hdev->lock ordering. Two concurrent listen() calls on the same broadcast socket can therefore both observe BT_BOUND. Caller A can attach connA and release the locks, then caller B can acquire them and attach connB before A publishes BT_LISTEN.

__iso_chan_add() checks whether connB already has a socket, but not whether the socket already has a connection. The second attachment overwrites iso_pi(sk)->conn, leaking the connA reference and leaving connA->sk intact. Socket teardown follows connB, so later events on connA can cause a stale socket access.

Recheck BT_BOUND and require iso_pi(sk)->conn to be NULL after taking both the HCI device and socket locks in iso_listen_bis(). The connection check also covers the interval between attachment and publication of BT_LISTEN. Reject a competing setup with -EBADFD through the existing unlock path before allocating another connection.

A recorded KASAN report from an instrumented kernel shows:

BUG: KASAN: slab-use-after-free in iso_sock_hold+0x119/0x1f0 Call Trace: iso_sock_hold+0x119/0x1f0 iso_conn_del+0xe4/0x270 hci_disconn_complete_evt+0x351/0x8c0 hci_event_packet+0x71b/0xb20 hci_rx_work+0x293/0x730

Allocated by task 93: sk_prot_alloc+0x113/0x220 sk_alloc+0x2b/0x6d0 bt_sock_alloc+0x29/0x370 iso_sock_alloc.constprop.0+0x19/0x300 iso_sock_create+0x94/0x100

Freed by task 93: kfree+0x121/0x3c0 __sk_destruct+0x42b/0x540 iso_sock_release+0x29d/0x340 __sock_release+0xa1/0x260 sock_close+0x10/0x20

Scores and how they were measured

CVSS base severity

7.8

Version 3.1As of Oct 24, 2026

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Measurement source

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

0.2%

Scored Oct 26, 2026Percentile 5.0%

Model and measurement source

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Linux kernel

Sources

Primary source
NVD CVE-2026-99013 (opens a new tab)
NVD record: description, CVSS (the CNA score is preferred), affected products, and publication date. Not evidence of exploitation.
Published Oct 23, 2026Checked Oct 26, 2026
Primary source
NVD CVE API 2.0 (opens a new tab)
The NVD API page that supplied this CVE record.
Published Date not suppliedChecked Oct 26, 2026
Primary source
FIRST measured EPSS score (opens a new tab)
Measured EPSS probability and percentile for CVE-2026-99013, scored 2026-10-26. This is a model estimate, not proof of exposure.
Published Oct 26, 2026Checked Oct 26, 2026

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, October 24). Linux kernel: Bluetooth: ISO: Reject concurrent BIS listener setup (CVE-2026-99013). https://kevwire.com/record/CVE-2026-99013

MLA

"Linux kernel: Bluetooth: ISO: Reject concurrent BIS listener setup (CVE-2026-99013)." KEVWire, 24 Oct. 2026, kevwire.com/record/CVE-2026-99013.

Chicago

KEVWire. "Linux kernel: Bluetooth: ISO: Reject concurrent BIS listener setup (CVE-2026-99013)." Last modified October 24, 2026. https://kevwire.com/record/CVE-2026-99013.

Evidence summary (plain text)

Linux kernel: Bluetooth: ISO: Reject concurrent BIS listener setup (Oct 23, 2026).
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: ISO: Reject concurrent BIS listener setup

iso_sock_listen() drops the socket lock before calling iso_listen_bis()
to preserve the hdev->lock ordering. Two concurrent listen() calls on
the same broadcast socket can therefore both observe BT_BOUND. Caller
A can attach connA and release the locks, then caller B can acquire
them and attach connB before A publishes BT_LISTEN.

__iso_chan_add() checks whether connB already has a socket, but not
whether the socket already has a connection. The second attachment
overwrites iso_pi(sk)->conn, leaking the connA reference and leaving
connA->sk intact. Socket teardown follows connB, so later events on
connA can cause a stale socket access.

Recheck BT_BOUND and require iso_pi(sk)->conn to be NULL after taking
both the HCI device and socket locks in iso_listen_bis(). The connection
check also covers the interval between attachment and publication of
BT_LISTEN. Reject a competing setup with -EBADFD through the existing
unlock path before allocating another connection.

A recorded KASAN report from an instrumented kernel shows:

  BUG: KASAN: slab-use-after-free in iso_sock_hold+0x119/0x1f0
  Call Trace:
   iso_sock_hold+0x119/0x1f0
   iso_conn_del+0xe4/0x270
   hci_disconn_complete_evt+0x351/0x8c0
   hci_event_packet+0x71b/0xb20
   hci_rx_work+0x293/0x730

  Allocated by task 93:
   sk_prot_alloc+0x113/0x220
   sk_alloc+0x2b/0x6d0
   bt_sock_alloc+0x29/0x370
   iso_sock_alloc.constprop.0+0x19/0x300
   iso_sock_create+0x94/0x100

  Freed by task 93:
   kfree+0x121/0x3c0
   __sk_destruct+0x42b/0x540
   iso_sock_release+0x29d/0x340
   __sock_release+0xa1/0x260
   sock_close+0x10/0x20
CVSS 7.8 (version 3.1; evidence as of Oct 24, 2026; https://nvd.nist.gov/vuln/detail/CVE-2026-99013).
EPSS 0.2% for the following 30 days, scored Oct 26, 2026 (https://api.first.org/data/v1/epss?cve=CVE-2026-99013&date=2026-10-26).
Sources:
NVD CVE-2026-99013: https://nvd.nist.gov/vuln/detail/CVE-2026-99013
NVD CVE API 2.0: https://services.nvd.nist.gov/rest/json/cves/2.0?pubStartDate=2026-10-12T13:35:55.142Z&pubEndDate=2026-10-26T13:35:55.142Z&resultsPerPage=500&startIndex=9000
FIRST measured EPSS score: https://api.first.org/data/v1/epss?cve=CVE-2026-99013&date=2026-10-26
Record ID: CVE-2026-99013.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.

About this data

This record was ingested from a data source. Retrieved: Oct 26, 2026, 19:40 UTC. Ingestion is not an independent editorial investigation.

NVD status: Received. Publication in the NVD is not evidence of exploitation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

Security, in focus.

Intelligence brief

The intelligence wire

Sources & methods

Editorial Evidence Review

CISA Known Exploited Vulnerabilities

GitHub Public Security Advisories

JPCERT/CC Japan Advisories

Google Project Zero Research

Google Security Research

NVD Recently Published CVEs

BleepingComputer Security Reporting

The Hacker News

SecurityWeek

Help Net Security

The Record (Recorded Future News)

Axios

TechCrunch Security

WIRED Security

The Verge (AI)

404 Media

Have I Been Pwned

DataBreaches.net

The HIPAA Journal

Anthropic

OpenAI

Google DeepMind

Microsoft Security blog

AI Incident Database

FIRST EPSS

CVE Program CVSS Enrichment

Context is part of the record.

A bounded source corpus

Evidence before attribution

Measurements, not invented urgency

What this does not assess

For AI agents and developers

Use the underlying data.

At a glance

What to do

What happened

Scores and how they were measured

CVSS base severity

EPSS probability

Related technology

Sources

NVD CVE-2026-99013 (opens a new tab)

NVD CVE API 2.0 (opens a new tab)

FIRST measured EPSS score (opens a new tab)

APA

MLA

Chicago

Evidence summary (plain text)