diff --git a/advisories/github-reviewed/2026/02/GHSA-wvr6-395c-5pxr/GHSA-wvr6-395c-5pxr.json b/advisories/github-reviewed/2026/02/GHSA-wvr6-395c-5pxr/GHSA-wvr6-395c-5pxr.json
index bf56dae9ad8e4..345ac4df5ffeb 100644
--- a/advisories/github-reviewed/2026/02/GHSA-wvr6-395c-5pxr/GHSA-wvr6-395c-5pxr.json
+++ b/advisories/github-reviewed/2026/02/GHSA-wvr6-395c-5pxr/GHSA-wvr6-395c-5pxr.json
@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-wvr6-395c-5pxr",
-  "modified": "2026-02-19T21:56:14Z",
+  "modified": "2026-02-19T21:56:17Z",
   "published": "2026-02-12T17:04:50Z",
   "aliases": [
     "CVE-2026-26063"
   ],
   "summary": "CediPay Affected by Improper Input Validation in Payment Processing",
-  "details": "A vulnerability in CediPay allows attackers to bypass input validation in the transaction API.\n\nAffected users: All deployments running versions prior to the patched release.\n\nRisk: Exploitation could result in unauthorized transactions, exposure of sensitive financial data, and compromise of payment integrity.\n\nSeverity: High — potential financial loss and reputational damage.\n\nPatches\nThe issue has been fixed in version 1.2.3.\n\nUsers should upgrade to 1.2.3 or later immediately.\n\nAll versions earlier than 1.2.3 remain vulnerable.\n\nWorkarounds\nIf upgrading is not immediately possible:\n\nRestrict API access to trusted networks or IP ranges.\n\nEnforce strict input validation at the application layer.\n\nMonitor transaction logs for anomalies or suspicious activity.\n\nThese mitigations reduce exposure but do not fully eliminate the vulnerability.\n\nReferences\nOWASP Input Validation Guidelines (owasp.org in Bing)\n\nCWE-20: Improper Input Validation\n\nGitHub Security Advisory Documentation (docs.github.com in Bing)",
+  "details": "A vulnerability in the CediPay transaction API allows attackers to bypass input validation.\n\n### Impact\nExploitation could result in unauthorized transactions, exposure of sensitive financial data, and compromise of payment integrity, leading to potential financial loss. All deployments running versions prior to the patched release are affected.\n\n### Patches\nThe issue has been fixed in version `1.2.3`. Users should upgrade to version `1.2.3` or later immediately. \n\n### Workarounds\nIf upgrading is not immediately possible, users can apply the following mitigations (note that these reduce exposure but do not fully eliminate the vulnerability):\n* Restrict API access to trusted networks or IP ranges.\n* Enforce strict input validation at the application layer.\n* Monitor transaction logs for anomalies or suspicious activity.",
   "severity": [
     {
       "type": "CVSS_V4",