CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Abacus AbaClik

product · product:abacus-abaclik

Coverage
1
first 2026-07-17 → last 2026-07-17
Latest activity
2026-07-17
NCSC-CH flags an unauthenticated RCE (CVSS 9.8) in Abacus ERP; reachable endpoint is the only prerequisite
Peak priority
high
1 high
Targets
public-sector
sectors: public-sector, finance · regions: switzerland
Sources cited
3
2 hosts

Action items (2)

Do-now tasks recorded on the entries about Abacus AbaClik, newest first. Check the date before acting on an older one.

  • Patch on-prem Abacus ERP to the fixed build (V2026 2026.201.17211 / V2025 2025.203.17044 / V2024 2024.204.16772) or apply the ServiceManager SilentHotfix, the SilentHotfix relies on a code-signing certificate known only to AbaClient ≥ 4.2, so on older clients the Abacus will fail to start until the client is updated or the hotfix reverted; EOL V2023-and-earlier has no fix and must be isolated or upgraded.
    2026-07-17NCSC-CH flags an unauthenticated RCE (CVSS 9.8) in…
  • Confirm the AbaClik / AbaClik.ai APIs are not reachable from untrusted networks; NCSC-CH notes they are exposed externally by default even for customers not using the mobile apps, which is the exposure the authenticated path-traversal file read abuses.
    2026-07-17NCSC-CH flags an unauthenticated RCE (CVSS 9.8) in…

Defender insights

What each entry about Abacus AbaClik tells a defender to do, newest first.

2026-07-17HIGHNCSC-CH flags an unauthenticated RCE (CVSS 9.8) in Abacus ERP; reachable endpoint is the only prerequisite

Story timeline

  1. 2026-07-17Abacus ERP: unauthenticated RCE (CVSS 9.8, no CVE) and authenticated path traversal in a widely-deployed Swiss ERP platform, flagged by NCSC-CH
    trending-vulnerabilitiesNCSC-CH flags an unauthenticated RCE (CVSS 9.8) in Abacus ERP; reachable endpoint is the only prerequisite

Hunting pivots

Releases covered
Abacus AbaClik
ATT&CK techniques (1 across 1 tactic)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-07-17/abacus-erp-unauth-rce-path-traversal-ncsc-ch · ATT&CK page ↗

Entries about Abacus AbaClik (1)

2026-07-17 · view entry permalink →

HIGHNATOA2

Abacus ERP: unauthenticated RCE (CVSS 9.8, no CVE) and authenticated path traversal in a widely-deployed Swiss ERP platform, flagged by NCSC-CH

Abacus Research AG (Wittenbach, SG) patched two unrelated flaws on 2026-07-15 that NCSC-CH surfaced the following day (NCSC-CH, 2026-07-16). The critical one is an unauthenticated remote code execution in the server-side handler of the proprietary Abacus client-server communication protocol: "the vulnerability allows remote code execution on the abacus server without user authentication," and "reachable Abacus Endpoints are the only prerequisite for an attack", no credentials, no user interaction (Abacus Research AG, 2026-07-15). The vendor states the flaw is not limited by license or option: every on-prem Abacus ERP installation is affected, and End-of-Life V2023-and-earlier builds remain vulnerable with no fix planned. The second flaw (CVSS 7.7) is a path traversal in two APIs tied to the AbaClik / AbaClik.ai mobile companion apps that lets an authenticated caller read a subset of server files outside the application's security realm; NCSC-CH's load-bearing point is that these APIs are network-exposed by default even for customers who do not use the mobile apps (Abacus Research AG, 2026-07-15).

Both were found through Abacus's own bug-bounty program and the vendor reports no indication of exploitation in the wild. Internet-facing on-prem deployments are the acute case; an internal-only Abacus still carries the flaw but with the attack surface reduced to the internal network.

If successfully exploited, the vulnerability allows remote code execution on the abacus server without user authentication.

Reachable Abacus Endpoints are the only prerequisite for an attack.

No, the vulnerability was found in our bugbounty program. We have no indications of a successful attack in the wild.

Abacus Research AG
vulnerability17 Jul 04:35Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • security.abacus.ch2 (67%)
  • security-hub.ncsc.admin.ch1 (33%)