# CVE-2026-82808: Inbox Foundry ActiveInbox Extension Google OAuth Client Secret service-worker.production-esm.js hard-coded credentials

> Hard-coded Google OAuth client secret in ActiveInbox extension allows remote attackers to bypass security controls and access data.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-gxhr-6gh9-279g

## What is CVE-2026-82808?

CVE-2026-82808 is a medium-severity vulnerability in ActiveInbox Extension, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in Inbox Foundry ActiveInbox Extension up to 7.10.24 on Chrome. Impacted is an unknown function of the file dist/service-worker.production-esm.js of the component Google OAuth Client Secret. Such manipulation leads to hard-coded credentials. The attack can be executed remotely. The exploit is publicly available and might be used. The vendor was informed beforehand about the issue. The support explains, that "[a]t the moment, the [bug bounty] programme is on hold while we work through a large number of existing reports."

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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


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

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

## Is CVE-2026-82808 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82808 is a medium-severity vulnerability in ActiveInbox Extension, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82808 exists.

Affected product: ActiveInbox Extension. 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-82808/ (Markdown: https://insights.sbomify.com/CVE-2026-82808/index.md)
```

## Sources

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

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