# CVE-2026-121024: Read-Only Shared Token Allows Modification of Monitoring Alerts in AxxonNet

Status: published. Published: 2026-11-03. Updated: 2026-11-03.

Incorrect Authorization (CWE-863) in the Health Monitoring service in AxxonSoft AxxonNet before 3.28.0 on Linux allows a remote attacker in possession of a shared report token, which is intended for read-only access, to create, modify or delete monitoring alerts via the monitoring API.

## Remediation

- fix: Upgrade AxxonNet to version 3.28.0 or later. Revoke and reissue shared report tokens that were distributed before the upgrade, and review the monitoring alert configuration for unauthorized changes. (source: CNA: AxxonSoft)

## Affected products and versions

- AxxonSoft / AxxonNet: ≥ 0; < 3.28.0 (affected, semver). Source: CNA: AxxonSoft; platforms: Linux

## Severity and prioritization

- CVSS 3.1: 5.4 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L; source: CNA: AxxonSoft

- CVSS 4.0: 5.3 (medium); CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N; source: CNA: AxxonSoft

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-863

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.axxonsoft.com/legal/axxonsoft-vulnerability-disclosure-policy/security-advisories#CVE-2026-121024 (CNA: AxxonSoft; vendor-advisory)

## Provenance

- CNA: AxxonSoft: https://www.cve.org/CVERecord?id=CVE-2026-121024; retrieved 2026-11-03; source updated 2026-11-03

Revision: 9ccdf1e35b57dcd139d45b4c3a205a6be693a8859201239a7c20bf06f18af378

Canonical: https://y2.dev/cve/CVE-2026-121024

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.