nday
CVE-2026-35501

Bypass of a configured island trust anchor underneath an insecure parent from an atacker-controlled NSEC record.

NLnet Labs / Unbound

公開当日に技術解析が確認されています。nday はまだ修正の根拠を取得していません。修正がないという意味ではありません。4 つの PoC ソースのいずれにも未掲載です。CISA KEV には現時点で未掲載です。

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

remote, unauthenticated
AV:N、PR:N、UI:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N (CVSS 3.1) from the CNA NLnet Labs
network
AV:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N (CVSS 3.1) from the CNA NLnet Labs
no authentication required
PR:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N (CVSS 3.1) from the CNA NLnet Labs
no user interaction
UI:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N (CVSS 3.1) from the CNA NLnet Labs
現在の段階
ANA
公開日時
CVSS 基本値
3.7 LOW v3.1

ライフサイクル

横軸は UTC。点=分単位、幅広の帯=日付のみ、白抜き=不明または推定。
日時不明
DIS公開
10-21T08:56Z
PAT修正
記録なし
ANA解析
10-21T09:06Z
POCPoC
記録なし
ITW悪用
記録なし
KEVKEV
記録なし

概要

When NLnet Labs Unbound 1.0.1 up to and including version 1.26.1 is configured with both a root trust anchor and an additional 'trust-anchor:' for an island-of-security zone whose parent is provably insecure under the root chain, a malicious actor with a forged NSEC reply with the SOA bit cleared can trick Unbound to treat the configured trust island as insecure. This happens because the DNSSEC validator in Unbound accepts and caches the NSEC insecure response bypassing the RRSIG validation that the validator was supposed to do. The acceptance of the NSEC record at the trust anchor apex was allowed due to and old fix for type DS and NSEC queries from clients when trust anchor for that name existed.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 3.1 vector from the CVE record, scored by the CNA NLnet Labs.

イベント履歴

+DIS公開

NLnet Labs が CVE レコードを公開。CVSS 基本値 3.7(注意)。

出典 cvelist · nday が に一括取り込み · 生データ
{
  "id": 420331,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-35501",
  "occurred_at": "2026-10-21T08:56:55.811Z",
  "observed_at": "2026-11-13T05:39:44.380581Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "version": "3.1",
      "base_score": 3.7,
      "base_severity": "LOW"
    },
    "ssvc": {
      "timestamp": "2026-10-29T19:05:15.135425Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-10-21T08:56:55.811Z",
    "assigner_short_name": "NLnet Labs"
  }
}
+ANA技術解析

oss-security メーリングリストへの投稿:「Unbound: 1.26.2 addresses multiple CVE items」。

出典 osssec 2026/q4/282 · nday が にリアルタイムで観測 · 生データ
{
  "id": 495713,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/282",
  "occurred_at": "2026-10-21T09:06:11Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/282",
  "detail": {
    "list": "oss-security",
    "author": "Yorgos Thessalonikefs",
    "subject": "Unbound: 1.26.2 addresses multiple CVE items",
    "is_reply": false
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

研究者の投稿

過去 7 日間に 0 人の研究者が言及

リストの研究者が X でこの CVE に触れた投稿です。原文のまま表示し、nday は検証していません。

リストの研究者が X でこの CVE に触れた投稿は、まだ収集していません。

Discussion

0 comments

No comments yet.