CVE-2026-41571

CRITICALNVD 9.49.4
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Note Mark is an open-source note-taking application. In version 0.19.2, IsPasswordMatch in backend/db/models.go falls back to a hard-coded bcrypt("null") placeholder whenever a user has no stored password. OIDC-registered users are created with an empty password, so anyone who submits password: "null" to the internal login endpoint receives a valid session for that user. The bypass is unauthenticated and requires no user interaction. This issue has been patched in version 0.19.3.

CVSS v3
9.4
EG Score
9.4(medium)
EPSS
21.4%
KEV
Not listed

Published

May 4, 2026

Last Modified

May 6, 2026

Advisory Details (2)

Auto-updated May 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

OIDC-registered users authenticated by submitting password "null" · Advisory · enchant97/note-mark · GitHub

https://github.com/enchant97/note-mark/security/advisories/GHSA-pxf8-6wqm-r6hh
generic

Release V0.19.3 · enchant97/note-mark · GitHub

https://github.com/enchant97/note-mark/releases/tag/v0.19.3

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/enchant97/note-mark/backend0.0.0-20260417132909-dea5530cc989

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 152 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 01:59 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
Show 75 more
  1. 2026-06-18 17:52 UTCEPSS rescore
  2. 2026-06-17 17:53 UTCEPSS rescore
  3. 2026-06-16 17:52 UTCEPSS rescore
  4. 2026-06-15 17:49 UTCEPSS rescore
  5. 2026-06-15 06:39 UTCEG score recompute
  6. 2026-06-15 03:01 UTCEG score recompute
  7. 2026-06-14 23:23 UTCEG score recompute
  8. 2026-06-14 19:44 UTCEG score recompute
  9. 2026-06-14 15:57 UTCEG score recompute
  10. 2026-06-14 11:47 UTCEG score recompute
  11. 2026-06-14 08:08 UTCEG score recompute
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 11:46 UTCEG score recompute
  16. 2026-06-12 08:09 UTCEG score recompute
  17. 2026-06-12 04:33 UTCEG score recompute
  18. 2026-06-12 00:56 UTCEG score recompute
  19. 2026-06-11 21:19 UTCEG score recompute
  20. 2026-06-11 17:43 UTCEG score recompute
  21. 2026-06-11 14:06 UTCEG score recompute
  22. 2026-06-11 14:00 UTCEPSS rescore
  23. 2026-06-11 10:29 UTCEG score recompute
  24. 2026-06-11 06:45 UTCEG score recompute
  25. 2026-06-11 02:45 UTCEG score recompute
  26. 2026-06-10 22:18 UTCEPSS rescore
  27. 2026-06-10 20:58 UTCEG score recompute
  28. 2026-06-10 17:18 UTCEG score recompute
  29. 2026-06-10 13:41 UTCEG score recompute
  30. 2026-06-10 13:22 UTCEPSS rescore
  31. 2026-06-10 13:22 UTCEPSS rescore
  32. 2026-06-10 10:04 UTCEG score recompute
  33. 2026-06-10 06:26 UTCEG score recompute
  34. 2026-06-10 02:49 UTCEG score recompute
  35. 2026-06-09 23:13 UTCEG score recompute
  36. 2026-06-09 17:11 UTCEG score recompute
  37. 2026-06-09 13:33 UTCEG score recompute
  38. 2026-06-09 09:56 UTCEG score recompute
  39. 2026-06-09 06:20 UTCEG score recompute
  40. 2026-06-09 02:42 UTCEG score recompute
  41. 2026-06-08 22:38 UTCEG score recompute
  42. 2026-06-08 14:17 UTCEPSS rescore
  43. 2026-06-08 14:17 UTCEPSS rescore
  44. 2026-06-08 13:11 UTCEG score recompute
  45. 2026-06-08 09:34 UTCEG score recompute
  46. 2026-06-08 05:57 UTCEG score recompute
  47. 2026-06-08 02:21 UTCEG score recompute
  48. 2026-06-07 22:44 UTCEG score recompute
  49. 2026-06-07 19:08 UTCEG score recompute
  50. 2026-06-07 15:31 UTCEG score recompute
  51. 2026-06-07 15:25 UTCEPSS rescore
  52. 2026-06-07 15:25 UTCEPSS rescore
  53. 2026-06-07 11:54 UTCEG score recompute
  54. 2026-06-07 08:17 UTCEG score recompute
  55. 2026-06-07 04:40 UTCEG score recompute
  56. 2026-06-07 04:40 UTCEG score recompute
  57. 2026-06-07 01:03 UTCEG score recompute
  58. 2026-06-06 21:26 UTCEG score recompute
  59. 2026-06-06 17:41 UTCEG score recompute
  60. 2026-06-06 14:04 UTCEG score recompute
  61. 2026-06-06 13:47 UTCEPSS rescore
  62. 2026-06-06 13:47 UTCEPSS rescore
  63. 2026-06-06 10:26 UTCEG score recompute
  64. 2026-06-06 06:49 UTCEG score recompute
  65. 2026-06-06 03:12 UTCEG score recompute
  66. 2026-06-05 23:35 UTCEG score recompute
  67. 2026-06-05 22:47 UTCEPSS rescore
  68. 2026-06-05 19:56 UTCEG score recompute
  69. 2026-06-05 16:19 UTCEG score recompute
  70. 2026-06-05 12:40 UTCEG score recompute
  71. 2026-06-05 09:03 UTCEG score recompute
  72. 2026-06-05 06:10 UTCEPSS rescore
  73. 2026-06-05 06:10 UTCEPSS rescore
  74. 2026-06-05 05:26 UTCEG score recompute
  75. 2026-06-05 01:49 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-41571?
CVE-2026-41571 is a critical vulnerability published on May 4, 2026. Note Mark is an open-source note-taking application. In version 0.19.2, IsPasswordMatch in backend/db/models.go falls back to a hard-coded bcrypt("null") placeholder whenever a user has no stored password. OIDC-registered users are created with an empty password, so anyone who submits password:…
When was CVE-2026-41571 disclosed?
CVE-2026-41571 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41571 actively exploited?
CVE-2026-41571 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41571?
CVE-2026-41571 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-41571?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41571, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41571

Explore →

Is Your Infrastructure Affected by CVE-2026-41571?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.