CVE-2026-7166
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability involving the exposure of sensitive data provided without adequate protection. The API exposes email and phone number data from the ‘email’ and ‘telefon’ fields. This vulnerability is also present in the local database, as it contains accessible sensitive information such as data on minors and municipal users. Successful exploitation of this vulnerability could allow an unauthenticated remote attacker to gain access to sensitive information and data.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn API endpoint exposes sensitive PII including email addresses and phone numbers ('telefon' field) without authentication or authorization controls. The underlying local database also contains accessible sensitive information including data on minors and municipal users, indicating inadequate access controls at the data layer. An unauthenticated remote attacker can directly query these endpoints or database to harvest this sensitive information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify API endpoints and test authenticationEnumerate all API endpoints in your environment. For each endpoint, attempt to access it without providing any authentication credentials (no API key, token, or session). Inspect HTTP response codes and returned data.Affected if Any endpoint returns sensitive PII (email addresses, phone numbers) or data about minors/municipal users without requiring authentication
-
Verify API authorization controlsIf authentication is present, test whether different user roles can access data belonging to other users or unauthorized resources. Submit requests with valid credentials but insufficient privileges and observe if PII is returned.Affected if Users can access PII belonging to other users or unauthorized records without proper role-based access controls
-
Inspect database encryption statusCheck database configuration files and settings for encryption at rest. Query the database directly to see if sensitive fields (emails, phone numbers, minor information, municipal user data) are stored in plaintext or encrypted format.Affected if Sensitive PII fields in the database are stored unencrypted or in plaintext format
-
Verify database access controlsReview database user permissions and network access policies. Determine whether the database is accessible only to authorized application services or if unauthorized network actors can connect directly.Affected if Database containing sensitive data is accessible to unauthorized parties or lacks proper network segmentation and access controls
-
Check for PII exposure in API responsesCapture and review API responses from all endpoints. Search for patterns matching email addresses, phone numbers, and other personally identifiable information in the returned payloads.Affected if API responses contain PII such as email addresses or phone numbers that the requesting user should not have access to
Your environment is affected if any API endpoint returns PII without requiring authentication, or if the local database stores sensitive data unencrypted and is accessible to unauthorized parties.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement authentication and role-based authorization on all API endpoints, add proper access controls to restrict database queries, and encrypt sensitive PII fields (email, phone) and data about minors at rest.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7166 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data