blinko authentication bypass in 2FA verification endpoint
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
The 2FA Endpoint of blinkospace blinko has an improper authentication flaw in its verify-2fa function. An attacker can reach it remotely over the network without logging in.
Written by a model
Original description
A weakness has been identified in blinkospace blinko up to 1.8.8. Affected is an unknown function of the file /api/auth/verify-2fa of the component 2FA Endpoint. This manipulation of the argument userId causes improper authentication. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 1.8.9 is able to address this issue. Patch name: 80e1c4ffaffe66a97df2b5d85fad864ff3691dc8. Upgrading the affected component is advised.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133502 (blinkospace blinko 2FA Endpoint verify-2fa improper authentication), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133502 (entry last updated 2026-11-20):
Affected:
- blinkospace blinko: versions 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, 1.8.7, 1.8.8
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133502 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133502 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/blinkospace/blinko/pull/1274
- https://github.com/blinkospace/blinko/commit/80e1c4ffaffe66a97df2b5d85fad864ff3691dc8
- https://github.com/blinkospace/blinko/releases/tag/1.8.9
- https://vuldb.com/vuln/440924
- https://vuldb.com/vuln/440924/cti
- https://vuldb.com/cve/CVE-2026-133502
- https://vuldb.com/submit/1049942
- https://github.com/blinkospace/blinko/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133502
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133502"}.Affected versions
- blinkospace blinko1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, 1.8.7, 1.8.8
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 11
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133502 |
| Record | NVD · CVE-2026-133502 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | gist.github.com · DReazer/fcc654ac4997e73cf2fed5127321dafa |
| Other links 8 | |
| Advisory | VulDB · Advisory #440924 |
| Advisory | VulDB · Threat intelligence #440924 |
| Advisory | VulDB · CVE-2026-133502 record |
| Advisory | VulDB · Submission #1049942 |
| Patch | GitHub · blinkospace/blinko · Pull request #1274 |
| Patch | GitHub · blinkospace/blinko · Commit 80e1c4ff |
| Patch | GitHub · blinkospace/blinko · Release 1.8.9 |
| Repository | GitHub · blinkospace/blinko · Repository |
Questions about CVE-2026-133502
Is CVE-2026-133502 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133502?
blinko: versions 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4 and 4 more.
Source: cve.now feed data
Related
- CVE-2026-85607Blinko 1.8.7 Cross-User AI Conversation Read and Write via message tRPC Router
- CVE-2026-23882Blinko: Admin RCE - MCP Server Command Injection
- CVE-2026-23482Blinko: Unauthorized Arbitrary File Read - /api/file/temp
- CVE-2026-85624Blinko 1.8.7 Cross-User Private Note Disclosure via noteReferenceList
- CVE-2026-23485Blinko: Unauthorized Path Traversal File Enumeration - music-metadata
- CVE-2026-23488Blinko: multiple interfaces in the comment feature allow unauthorized access
No corrections so far. Something wrong on this page? Report an error.