ETK-2026-544Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-4gx4-x7gm-4xq8 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other:AiSOC (services/api) <= 16.0.0
fixed in 16.0.1
CWE-863 Incorrect Authorization
ETK-2026-544, no cve assigned
cvss7.0ethiack provisional
17d 05h 41msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
waiting for further signals−0.3dtrigger signal +0d
+5d
+10d
+15d

description

AiSOC services/api can authorize tenant RBAC role assignments using a user's static role instead of their effective database-backed permissions. An authenticated tenant user restricted to users:write may be able to grant their own account an existing role with additional same-tenant permissions when database-backed RBAC is configured and their static role permits those permissions.

mitigation

Upgrade AiSOC services/api to version 16.0.1. Until upgraded, restrict access to role-assignment functions and review tenant RBAC assignments for unexpected self-granted roles.

fixed in 16.0.1

check
no
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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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: an exploit technique exists, 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-04 06:51Z

this entry in the feed

GET /api/v1/feed/ETK-2026-544

{
  "etk_id": "ETK-2026-544",
  "cve_id": null,
  "display_id": "ETK-2026-544",
  "ghsa_id": "GHSA-4gx4-x7gm-4xq8",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Incorrect authorization in AiSOC role assignment",
  "summary": "AiSOC services/api can authorize tenant RBAC role assignments using a user's static role instead of their effective database-backed permissions. An authenticated tenant user restricted to `users:write` may be able to grant their own account an existing role with additional same-tenant permissions when database-backed RBAC is configured and their static role permits those permissions.",
  "mitigation": "Upgrade AiSOC services/api to version 16.0.1. Until upgraded, restrict access to role-assignment functions and review tenant RBAC assignments for unexpected self-granted roles.",
  "vendor": "other",
  "product": "other:AiSOC (services/api)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 16.0.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "16.0.1"
      ],
      "package_name": "AiSOC (services/api)",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.82021483333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-04T06:51:47+00:00",
      "days": -16.955496216122686,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:47:41.896060+00:00",
      "url": "https://github.com/beenuar/AiSOC/security/advisories/GHSA-4gx4-x7gm-4xq8"
    }
  }
}

published 2026-10-04 08:22Z
last change 2026-10-21 05:31Z

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.