# CVE-2026-103053: AiSOC 9.0.0 before 12.0.0 Missing Authentication on Actions Service Response-Action API

> Unauthenticated attackers can execute containment actions and modify data when development mode is enabled with an empty service token.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-g4h7-p63q-r8r4, GHSA-xjh9-76cm-4wjr

## What is CVE-2026-103053?

CVE-2026-103053 is a medium-severity missing authorization vulnerability in beenuar AiSOC, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AiSOC versions 9.0.0 before 12.0.0 fail to enforce authentication on the response-action API endpoints when AISOC_DEV_MODE is enabled and AISOC_ACTIONS_SERVICE_TOKEN is empty in the default Docker Compose deployment. Unauthenticated attackers can list response-action integrations, submit and approve actions on behalf of arbitrary principals, and dispatch containment actions using vendor credentials.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-103053?


## How do I fix CVE-2026-103053?

No fix has been published for CVE-2026-103053 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103053 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-103053 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103053 and fix it if it is affected.

What it is: CVE-2026-103053 is a medium-severity missing authorization vulnerability in beenuar AiSOC, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-103053 exists.

Affected product: beenuar AiSOC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103053/ (Markdown: https://insights.sbomify.com/CVE-2026-103053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103053
- OSV: https://osv.dev/vulnerability/CVE-2026-103053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103053/
Summaries are generated and may contain mistakes; the official description above is the record.