{
  "id": "CVE-2026-105482",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-105482",
  "published_at": "2026-10-23T16:15:05.831Z",
  "vendor": "nodejs",
  "product": "node",
  "cvss": {
    "score": 7.4,
    "source": "cna",
    "vector": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": {
    "created_at": "2026-10-21T15:41:53Z",
    "first_seen_at": "2026-11-14T11:25:11.578Z",
    "days_after_publication": -2,
    "repo": "CaterMaoZi/CVE-2026-105482-POC",
    "source": "github"
  },
  "poc_repo_count": 4,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options.\r\n\r\nBecause the name is passed to c-ares as a C string, resolving attacker.example\\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated.\r\n\r\nThis vulnerability affects Node.js 26.x, 24.x, and 22.x.",
  "cwe": "CWE-284",
  "cvss_by_source": {
    "cna": 7.4
  },
  "repos": [
    {
      "repo": "CaterMaoZi/CVE-2026-105482-POC",
      "url": "https://github.com/CaterMaoZi/CVE-2026-105482-POC",
      "created_at": "2026-10-21T15:41:53Z",
      "first_seen_at": "2026-11-14T11:25:11.578Z",
      "stars": 9,
      "is_poc": "yes",
      "kind": "exploit",
      "suspicion_score": 0,
      "suspicious": false,
      "suspicion_reasons": [],
      "status": "analyzed",
      "owner_created_at": "2023-02-22T16:22:00Z"
    },
    {
      "repo": "CompleTech-Security/node-cve-2026-105482-check",
      "url": "https://github.com/CompleTech-Security/node-cve-2026-105482-check",
      "created_at": "2026-10-23T23:46:49Z",
      "first_seen_at": "2026-11-14T11:25:11.578Z",
      "stars": 0,
      "is_poc": "yes",
      "kind": "scanner",
      "suspicion_score": 30,
      "suspicious": false,
      "suspicion_reasons": [
        "owner account created less than 7 days before the repo"
      ],
      "status": "analyzed",
      "owner_created_at": "2026-10-24T07:04:53Z"
    },
    {
      "repo": "completetech-security/node-cve-2026-105482-check",
      "url": "https://github.com/completetech-security/node-cve-2026-105482-check",
      "created_at": "2026-10-23T23:46:49Z",
      "first_seen_at": "2026-11-14T11:25:11.578Z",
      "stars": 0,
      "is_poc": "yes",
      "kind": "scanner",
      "suspicion_score": 30,
      "suspicious": false,
      "suspicion_reasons": [
        "owner account created less than 7 days before the repo"
      ],
      "status": "analyzed",
      "owner_created_at": "2026-10-24T07:04:53Z"
    },
    {
      "repo": "EthanTech-Offical/CVE-2026-105482-Reproduce",
      "url": "https://github.com/EthanTech-Offical/CVE-2026-105482-Reproduce",
      "created_at": "2026-10-28T01:06:08Z",
      "first_seen_at": "2026-11-14T11:25:11.578Z",
      "stars": 0,
      "is_poc": "yes",
      "kind": "exploit",
      "suspicion_score": 0,
      "suspicious": false,
      "suspicion_reasons": [],
      "status": "analyzed",
      "owner_created_at": "2026-06-05T13:35:26Z"
    }
  ],
  "remediation": {
    "affected": [
      {
        "vendor": "nodejs",
        "product": "node",
        "ranges": [
          "\u003e= 22.23.3, \u003c= 22.23.3",
          "\u003e= 24.22.0, \u003c= 24.22.0",
          "\u003e= 26.12.0, \u003c= 26.12.0"
        ],
        "fixed_in": null
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
