Read the docs
TI-2019-12255 Aliases CVE-2019-16281GHSA-q5m9-8685-c94f

Ptarmigan before 0.2.3 lacks API token validation, e.g., an "if (token === apiToken)…

Priority LOW 35CWE-295Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Spoofing
Confidentiality · integrity · availability
None · High · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-295.

Summary

Ptarmigan before 0.2.3 lacks API token validation, e.g., an "if (token === apiToken) {return true;} return false;" code block.

Why it matters now

EPSS 0.01277 70th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:ptarmigan_project:ptarmigan:*:*:*:*:*:*:*:*before 0.2.3VulnerablePtarmigan Project
  • cpe:2.3:a:ptarmigan_project:ptarmigan:*:*:*:*:*:*:*:* Versions before 0.2.3 Vulnerable ·Ptarmigan Project

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2019-16281
  2. 2026-10-03 Alias added: GHSA-q5m9-8685-c94f

References

Sources