# CVE-2026-2676: GoogTech sms-ssm API LoginInterceptor.java preHandle improper authorization

> Remote attackers can bypass authentication in the GoogTech sms-ssm API due to improper authorization checks in the login interceptor.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-63wr-vhhf-qrpx

## What is CVE-2026-2676?

CVE-2026-2676 is a medium-severity missing authorization vulnerability in GoogTech sms-ssm, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-2676?


## How do I fix CVE-2026-2676?

No fix has been published for CVE-2026-2676 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2676 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2676 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2676 and fix it if it is affected.

What it is: CVE-2026-2676 is a medium-severity missing authorization vulnerability in GoogTech sms-ssm, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2676 exists.

Affected product: GoogTech sms-ssm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2676/ (Markdown: https://insights.sbomify.com/CVE-2026-2676/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2676
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2676
- OSV: https://osv.dev/vulnerability/CVE-2026-2676

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2676/
Summaries are generated and may contain mistakes; the official description above is the record.