← back to feed
CVE-2026-111606

CVE-2026-111606

validatedZero produced an exploit or a check.

EUVD-2026-103028 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
hcengineering Huly Platform <= 0.7.432
CWE-862 Missing Authorization
ETK-2026-1798Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss8.6cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
+1h16mTTV
37mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+76magent stopped
0
+15min
+30min
+45min
+60min

description

Huly Platform versions through 0.7.432 do not properly authorize person-merge requests. An authenticated user who knows relevant person identifiers may link an attacker-controlled social identity to another account and potentially gain control of that account through login or recovery flows.

mitigation

Restrict or disable access to the mergeSpecifiedPersons account RPC where deployment controls allow, and review merge activity for unexpected account associations. Apply a vendor-provided update when one becomes available.

check
available
exploit
no
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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.24%13th percentile
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 17:38Z
Δ 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

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-16 17:38Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-111606

this entry in the feed

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

{
  "etk_id": "ETK-2026-1798",
  "cve_id": "CVE-2026-111606",
  "display_id": "CVE-2026-111606",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-103028",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Huly Platform person merging",
  "summary": "Huly Platform versions through 0.7.432 do not properly authorize person-merge requests. An authenticated user who knows relevant person identifiers may link an attacker-controlled social identity to another account and potentially gain control of that account through login or recovery flows.",
  "mitigation": "Restrict or disable access to the mergeSpecifiedPersons account RPC where deployment controls allow, and review merge activity for unexpected account associations. Apply a vendor-provided update when one becomes available.",
  "vendor": "hcengineering",
  "product": "Huly Platform",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.7.432"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Huly Platform",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0024,
  "epss_percentile": 0.1398,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 37.003923416666666,
  "t0_at": "2026-10-16T17:38:47.643000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-16T18:54:59.226343+00:00",
      "days": 0.052911844247685184,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T17:38:47.643000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-16T17:38:47.643000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T17:38:47.643000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111606"
    }
  }
}

published 2026-10-16 18:17Z
last change 2026-10-21 13:29Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.