CVE-2026-108047

validatingZero is analyzing and reversing it now.

EUVD-2026-115796 ↗

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.
AM System ALO Suite 25_09_15.03_35
ETK-2026-3367Zero's internal tracking ID, independent of the CVE number., permanent identifier
32mrunning
patch analysiscurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0hvalidating
0
+1h
+2h
+3h
+4h
+5h

description

ALO Suite's user-invitation function does not adequately enforce privilege assignment on the server. An unauthenticated attacker who can modify an invitation request may grant administrator access to a newly invited account.

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

mitigation

Disable or restrict access to the user-invitation endpoint until server-side privilege validation is in place. Limit who can initiate invitations and review newly created accounts for unexpected administrative roles.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 12:25Z
Δ 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-03 12:25Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3367",
  "cve_id": "CVE-2026-108047",
  "display_id": "CVE-2026-108047",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-115796",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Authorization bypass in ALO Suite user invitations",
  "summary": "ALO Suite's user-invitation function does not adequately enforce privilege assignment on the server. An unauthenticated attacker who can modify an invitation request may grant administrator access to a newly invited account.",
  "mitigation": "Disable or restrict access to the user-invitation endpoint until server-side privilege validation is in place. Limit who can initiate invitations and review newly created accounts for unexpected administrative roles.",
  "vendor": "AM System",
  "product": "ALO Suite",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "25_09_15.03_35"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "ALO Suite",
      "purl": null
    }
  ],
  "cwes": null,
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.906609366666668,
  "t0_at": "2026-11-03T12:25:58.988000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T12:25:58.988000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T12:25:58.988000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108047"
    }
  }
}

published 2026-11-03 12:55Z
last change 2026-11-03 16:32Z

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.