dbcve.org
Axxon OneApplication · Axxonsoft

CVE-2025-10226

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-10
Fix available
A fix is available. Upgrade to after 2.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Dependency on Vulnerable Third-Party Component (CWE-1395) in the PostgreSQL backend in AxxonSoft Axxon One (C-Werk) 2.0.8 and earlier on Windows and Linux allows a remote attacker to escalate privileges, execute arbitrary code, or cause denial-of-service via exploitation of multiple known CVEs present in PostgreSQL v10.x, which are resolved in PostgreSQL 17.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AxxonSoft Axxon One (C-Werk) 2.0.8 and earlier bundles a vulnerable PostgreSQL v10.x backend containing multiple known CVEs that were later fixed in PostgreSQL 17.4. Remote attackers can exploit these PostgreSQL vulnerabilities to escalate privileges, execute arbitrary code, or cause denial-of-service.

MitigationUpdate PostgreSQL to version 17.4 or later, or upgrade AxxonSoft Axxon One to a version that ships with the patched PostgreSQL release; verify application compatibility after the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Axxon OneApplication
Affected:<= 2.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Axxon One is installed
    Check for the presence of Axxon One installation directory (commonly C:\Program Files\AxxonSoft\Axxon One on Windows or /opt/axxonsoft/axxon-one on Linux). Look for executables such as C-Werk.exe, axton.exe, or service processes named 'Axxon One' or 'C-Werk'.
    Affected if Axxon One software is present on the system
  2. Determine Axxon One version
    Locate version information in the installation: check for a version.txt, about dialog, or registry key (HKLM\SOFTWARE\AxxonSoft\AxxonOne\Version on Windows). On Linux, inspect /opt/axxonsoft/axxon-one/version or run the axxonone --version command if available.
    Affected if The installed version is 2.0.8 or earlier
  3. Locate bundled PostgreSQL version
    Find the PostgreSQL data directory bundled with Axxon One (typically under the Axxon One installation folder, such as postgresql\data or ../database). Check the PG_VERSION file inside the data directory, or run: pg_ctl --version from the bundled PostgreSQL bin folder.
    Affected if The PostgreSQL version shown is 10.x (such as 10.x, 10.0, 10.1, etc.) indicating the vulnerable release
  4. Verify PostgreSQL is network-accessible
    Check PostgreSQL configuration files (postgresql.conf and pg_hba.conf) in the bundled PostgreSQL data directory. Look for listen_addresses and pg_hba.conf entries allowing remote connections. Also check if port 5432 (default PostgreSQL) is open using netstat -an | grep 5432.
    Affected if PostgreSQL is configured to accept remote connections (listen_addresses set to '*' or non-localhost IP, or pg_hba.conf permits non-localhost authentication)

The environment is affected if Axxon One version 2.0.8 or earlier is installed with bundled PostgreSQL 10.x that is network-accessible, as attackers can exploit the vulnerable PostgreSQL component for privilege escalation or code execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.8
Interim mitigation

Update PostgreSQL to version 17.4 or later, or upgrade AxxonSoft Axxon One to a version that ships with the patched PostgreSQL release; verify application compatibility after the update.

Recommended fix High confidence

Axxon One version containing PostgreSQL 17.4+ (check vendor release notes for 2.0.9 or later)

  1. Verify the current PostgreSQL version bundled with or used by Axxon One installation
  2. If Axxon One bundles PostgreSQL: Upgrade Axxon One to a version that ships with PostgreSQL 17.4 or later (if available)
  3. If PostgreSQL is standalone: Upgrade PostgreSQL to version 17.4 or later while ensuring compatibility with Axxon One
  4. After upgrading PostgreSQL, run any necessary database migration scripts provided by AxxonOne
  5. Verify the new PostgreSQL version by running: psql --version
  6. Restart Axxon One services to ensure the new PostgreSQL instance is utilized
Caveat Ensure database compatibility between Axxon One and PostgreSQL 17.x; backup existing database before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Axxon One Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10226 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data