CVE-2026-76876: puemos craftplan · Missing Authorization
Affects puemos craftplanSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 0.5.1 soon.
Data as of 19 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.2 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.9 |
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.5.1
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade puemos craftplan to 0.5.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| puemoscraftplan | Affected
| Fixed in– |
GitHubcraftplanpkg:github/craftplanOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to craftplan version 0.5.1 or later, where this broken access control vulnerability has been fixed. No other mitigations are indicated by the vendor advisory.
Description
Craftplan versions before 0.5.1 have a broken access control vulnerability that allows unauthenticated attackers to read sensitive credentials. The flaw is due to an unconditional authorization policy on the Settings resource, permitting GET requests to retrieve decrypted SMTP passwords and email API keys without identity verification. This vulnerability is fixed in version 0.5.1.