CVE-2026-105133
The record is as the index held it on 2026-10-18. The KEV listing and the EPSS score were read on 2026-10-25. The score is dated to the day it became true. The KEV state is dated to that read. Changes between those two dates are not all shown.
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
Ahsay AhsayCBS API ApiStructsAction.java checkSysPwd improper authentication
rank 79 = 40 + 17 + 12 + 0 + 10
rank@v1 · act now
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.79236 · CISA KEV listed · without this subject the record ranks 39
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 6.9, from the CNA · without this subject the record ranks 62
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
rose on 2026-10-25 · without this subject the record ranks 67
How much of the world it touches
NVD CPE configurations
0 products in the CPE ranges · without this subject the record ranks 79
Someone else already set the date
CISA KEV remediation due date
CISA remediation date held · without this subject the record ranks 69
Hindsight · the state
Foresight · where to check next
This record is one instance of CWE-287, improper authentication. The index holds 5176 prior instances of this class, 49 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1
Running Ahsay AhsayCBS? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Check your stack in the mirror · True as of 25 Oct 2026
Set up a watchlist (free with an account: one stack of three products)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.
Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Exploited in the wild · CISA KEV listed, 2026-10-14.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published
- RUNG 3Exploited in the wild · CISA KEV listed2026-10-14receipt
- RUNG 4Ransomware campaign use known
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
$2.27M = $4.99M incident cost x 0.5743756121449558 exposure x 0.79236 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
What it is stated by the CNA
A vulnerability was detected in Ahsay AhsayCBS up to 10.3.2. This affects the function checkSysPwd of the file com/ahsay/obs/api/ApiStructsAction.java of the component API. Performing a manipulation of the argument random results in improper authentication. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 10.3.4 is able to mitigate this issue. It is recommended to upgrade the affected component. receipt
check it yourself vuldb.com vuldb.com vuldb.com vuldb.com ahsay.com receipt
Dated events
Movement the material steps
Show all 3 observations
3 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The pattern, elsewhere
This record is one instance of CWE-287, improper authentication. The index holds 5176 prior instances of this class, 49 KEV-listed. The nearest of its KEV-listed records are drawn beside this. cwe-consequences@4.20
"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1
5176 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.
No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2026-105133.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.