dbcve.org
Antikor Next Generation FirewallOperating system · Epati

CVE-2026-2624

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 2.0.1301 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
Missing Authentication for Critical Function vulnerability in ePati Cyber ​​Security Technologies Inc. Antikor Next Generation Firewall (NGFW) allows Authentication Bypass. This issue affects Antikor Next Generation Firewall (NGFW): from v.2.0.1298 before v.2.0.1301.

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

This is an authentication bypass vulnerability in ePati's Antikor Next Generation Firewall where a critical function lacks proper authentication checks. An unauthenticated remote attacker can exploit this to bypass authentication and access sensitive firewall management functions, potentially gaining full control over the security device and the network it protects.

MitigationUpgrade the Antikor NGFW to version 2.0.1301 or later. If immediate patching is not possible, restrict network access to the firewall management interfaces using network segmentation or firewall rules to limit exposure to trusted administrative networks.

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
Antikor Next Generation FirewallOperating system
Affected:>= 2.0.1298, < 2.0.1301

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 the installed Antikor NGFW version
    Access the firewall administrative interface (web UI or CLI) and locate the system version or firmware version information, typically found under System Status, About, or Version sections
    Affected if The displayed version falls within the range 2.0.1298 or higher but below 2.0.1301
  2. Confirm the version through CLI if available
    If the firewall provides a command-line interface, execute the appropriate command to display the firmware version (for example, 'show version' or 'system info')
    Affected if The reported version matches 2.0.1298 through 2.0.1300 (any version before 2.0.1301)
  3. Verify network exposure of the management interface
    Determine if the administrative interface or API endpoints are reachable from untrusted networks or the public internet
    Affected if The management interface is exposed externally and the installed version is vulnerable
  4. Review authentication and access logs
    Examine the firewall logs for successful authentication events from unexpected IP addresses, particularly those occurring without prior login attempts or using atypical session patterns
    Affected if Logs show administrative access from unknown sources or sessions that bypassed normal authentication workflows

The environment is affected if the installed Antikor NGFW version is 2.0.1298 or higher but lower than 2.0.1301, and the management interface is network-accessible.

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 2.0.1301 or later
Fixed in 2.0.1301
Interim mitigation

Upgrade the Antikor NGFW to version 2.0.1301 or later. If immediate patching is not possible, restrict network access to the firewall management interfaces using network segmentation or firewall rules to limit exposure to trusted administrative networks.

Recommended fix High confidence

Upgrade to Antikor NGFW version 2.0.1301

  1. 1. Identify current Antikor NGFW version by accessing the admin interface or running: show version (or equivalent CLI command)
  2. 2. Confirm the installed version is >= 2.0.1298 and < 2.0.1301 to confirm vulnerability exposure
  3. 3. Download the patched version 2.0.1301 from the vendor (ePati Cyber Security Technologies Inc.) or authorized distribution channel
  4. 4. Review vendor release notes for version 2.0.1301 to understand any specific upgrade requirements or注意事项
  5. 5. Create a backup of the current NGFW configuration before upgrading
  6. 6. Execute the upgrade following the vendor's standard upgrade procedure (typically via admin interface or CLI: upgrade <image-file> or similar)
  7. 7. After upgrade completes, verify the new version is 2.0.1301 using: show version
  8. 8. Confirm critical functions are operational and the authentication mechanism is functioning correctly
Caveat Review vendor release notes for version 2.0.1301; minor version upgrades typically preserve configuration but always backup first

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

Fix this in Antikor Next Generation Firewall Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2624 — 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-2026-2624 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