INCIBE-CERT Reports Critical Tankuam Places Account Takeover Flaw
Tech GuruQuick Answer
INCIBE-CERT reports an account-takeover flaw in Tankuam Places: a password-recovery token was not bound to the requested account. Kompini says the service was corrected on November 25, 2025. Customers should obtain confirmation that their service is covered; the notice does not identify a downloadable fixed version.
Confirm Scope And Apply The Supported Fix
What to do now: Identify the Tankuam Places service and responsible Kompini contact. Obtain written confirmation of the managed correction and review suspicious password-reset or administrator-account activity.
Last verified: 2026-09-22 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Kompini Tankuam Places deployments before the November 25, 2025 coordinated fix |
|---|---|
| Advisory | INCIBE-CERT CVE-2026-93556 |
| CVE | CVE-2026-93556 |
| INCIBE advisory publication | 2026-09-22 (date shown by INCIBE) |
| Recorded source timestamp (historical snapshot) | 2026-09-22 10:15:28.526 UTC |
| Affected versions | Tankuam Places deployments before the managed correction applied by Kompini on November 25, 2025. |
| Fixed version | The Kompini-managed correction applied November 25, 2025; obtain current service status from Kompini |
| CVSS base score | 9.3 (CVSS v4.0) |
| CVSS severity | Critical |
| Exploitation status | INCIBE's advisory marks exploitation as 'No' as of the reviewed source. This is not proof that a particular deployment has never been compromised. |
What Changed
INCIBE-CERT reports that the password-recovery endpoint did not bind its JWT to the requested user identifier, allowing an unauthenticated attacker to reset arbitrary accounts, including administrators. The authority states that Kompini fixed the service on November 25, 2025.
What To Validate Now
- Inventory. Record service URLs, tenant or deployment identifiers, administrative account owners and the vendor's correction confirmation.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Tankuam Places deployments before the managed correction applied by Kompini on November 25, 2025. Do not infer applicability from product family or severity alone.
- Remediate. Confirm the November 25, 2025 correction with Kompini for the actual service. Do not interpret that date as an installable package version or assume a particular deployment was covered without confirmation.
- Validate. Using authorized test accounts, confirm password recovery remains bound to the intended account. Keep vendor confirmation separate from incident review; a corrected service does not establish that earlier account takeover never occurred.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Do not run cross-account reset tests against real users. Preserve reset/audit records before account remediation, and coordinate any access restriction or recovery with the service owner.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
