CVE-2026-119039

validatingZero is analyzing and reversing it now.

GHSA-hx9j-f48g-rh4h ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Defender Security >= 4.9.0, < 6.4.1
fixed in 6.4.1
ETK-2026-4246Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Defender Security versions before 6.4.1 may treat a client-controlled IP address as trustworthy for security decisions. An unauthenticated attacker could bypass IP-based restrictions, appear as an allowlisted address, or cause misleading activity-log entries when such address data is accepted.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade Defender Security to version 6.4.1 or later. Until upgraded, restrict exposure to untrusted clients and review IP-based access controls and logs for reliance on client-provided address information.

fixed in 6.4.1

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 06:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-12 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-119039

{
  "etk_id": "ETK-2026-4246",
  "cve_id": "CVE-2026-119039",
  "display_id": "CVE-2026-119039",
  "ghsa_id": "GHSA-hx9j-f48g-rh4h",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Improper client IP trust in Defender Security",
  "summary": "Defender Security versions before 6.4.1 may treat a client-controlled IP address as trustworthy for security decisions. An unauthenticated attacker could bypass IP-based restrictions, appear as an allowlisted address, or cause misleading activity-log entries when such address data is accepted.",
  "mitigation": "Upgrade Defender Security to version 6.4.1 or later. Until upgraded, restrict exposure to untrusted clients and review IP-based access controls and logs for reliance on client-provided address information.",
  "vendor": null,
  "product": "Defender Security",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.9.0, < 6.4.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.4.1"
      ],
      "package_name": "Defender Security",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-12T06:00:07.223000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T06:00:07.223000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T06:00:07.223000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119039"
    }
  }
}

published 2026-11-12 06:32Z
last change 2026-11-12 06:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.