How severe is CVE-2026-26063?

No CVSS score has been assigned to CVE-2026-26063 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-26063?

CVE-2026-26063 affects the following packages: cedipay-core (npm). Ecosystems affected: npm.

How do I fix CVE-2026-26063?

Update cedipay-core to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26063 is resolved across your whole dependency graph.

How do I detect CVE-2026-26063 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cedipay-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-26063 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-26063 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-26063 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-26063?

CVE-2026-26063 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-26063?

CVE-2026-26063 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-26063 published, and has it been updated?

CVE-2026-26063 was published on February 12, 2026 and was last updated on February 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-26063 — cedipay-core

CVE-2026-26063 is a Improper Input Validation vulnerability in cedipay-core. A fix is available for cedipay-core — see the affected versions and patch details below.

CediPay Affected by Improper Input Validation in Payment Processing

Published

Feb 12, 2026

Updated

Feb 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 17, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-26063.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.06%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦cedipay-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability in CediPay allows attackers to bypass input validation in the transaction API.

Affected users: All deployments running versions prior to the patched release.

Risk: Exploitation could result in unauthorized transactions, exposure of sensitive financial data, and compromise of payment integrity.

Severity: High — potential financial loss and reputational damage.

Patches The issue has been fixed in version 1.2.3.

Users should upgrade to 1.2.3 or later immediately.

All versions earlier than 1.2.3 remain vulnerable.

Workarounds If upgrading is not immediately possible:

Restrict API access to trusted networks or IP ranges.

Enforce strict input validation at the application layer.

Monitor transaction logs for anomalies or suspicious activity.

These mitigations reduce exposure but do not fully eliminate the vulnerability.

References OWASP Input Validation Guidelines (owasp.org in Bing)

CWE-20: Improper Input Validation

GitHub Security Advisory Documentation (docs.github.com in Bing)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`cedipay-core`	all versions	1.2.3`npm install cedipay-core@1.2.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cedipay-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cedipay-core to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26063 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

A vulnerability in CediPay allows attackers to bypass input validation in the transaction API. Affected users: All deployments running versions prior to the patched release. Risk: Exploitation could result in unauthorized transactions, exposure of sensitive financial data, and compromise of payment integrity. Severity: High — potential financial loss and reputational damage. Patches The issue has been fixed in version 1.2.3. Users should upgrade to 1.2.3 or later immediately. All versions earlier than 1.2.3 remain vulnerable. Workarounds If upgrading is not immediately possible: Restri

O3 Security · Impact-Aware SCA

Is CVE-2026-26063 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works