dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-2676

MEDIUM · 6.3 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A weakness has been identified in GoogTech sms-ssm up to e8534c766fd13f5f94c01dab475d75f286918a8d. Affected by this issue is the function preHandle of the file LoginInterceptor.java of the component API Interface. Executing a manipulation can lead to improper authorization. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed.

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 confidence

A weakness in GoogTech sms-ssm's LoginInterceptor.java allows improper authorization in the API Interface. The preHandle function, which typically performs authentication/authorization checks before request processing, fails to properly enforce authorization controls on certain API endpoints. This allows remote attackers to access protected resources without proper authorization. The public availability of an exploit increases risk.

MitigationReview and fix the authorization logic in LoginInterceptor.java's preHandle method to ensure all API endpoints require proper authentication/authorization checks before granting access. Implement role-based or permission-based access controls consistent with security best practices.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if GoogTech sms-ssm is deployed
    Search for the sms-ssm application in your environment. Check for directories or components named 'sms-ssm', 'GoogTech', or similar. Review your application inventory or deployed web applications.
    Affected if GoogTech sms-ssm is present in the environment
  2. Locate LoginInterceptor.java
    Search the application's source code or deployed files for LoginInterceptor.java. Common paths may include src directories under controller, interceptor, or security packages.
    Affected if LoginInterceptor.java exists in the application codebase
  3. Inspect the preHandle method in LoginInterceptor.java
    Open LoginInterceptor.java and locate the preHandle method. Review its implementation to see which API endpoints it processes and what authorization logic it performs.
    Affected if The preHandle method exists but may have incomplete authorization checks
  4. Test API endpoint access without authentication
    Identify API endpoints in the application. Attempt to access protected endpoints directly (without providing valid credentials or session tokens) using tools like curl or browser dev tools.
    Affected if Protected API endpoints are accessible without proper authentication credentials
  5. Review endpoint configuration or whitelist
    Check if certain endpoints are explicitly excluded from authentication in LoginInterceptor.java configuration, security XML files, or annotation-based security settings.
    Affected if Certain API endpoints are excluded or bypassed from the authorization checks in the preHandle logic

A user is affected if GoogTech sms-ssm is deployed and the LoginInterceptor.java preHandle method fails to enforce authorization on some API endpoints, allowing unauthenticated access to protected resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and fix the authorization logic in LoginInterceptor.java's preHandle method to ensure all API endpoints require proper authentication/authorization checks before granting access. Implement role-based or permission-based access controls consistent with security best practices.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2676 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2676 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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