Poly Video - Sensitive Data Might Be Written to Log File
In limited scenarios, sensitive data might be written to the log file if an admin uses Microsoft Teams Admin Center (TAC) to make device configuration changes. The affected log file is visible only to users with admin credentials. This is limited to Microsoft TAC and does not affect configuration changes made using the provisioning server or the device WebUI.
- Published
- Dec 16, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 32th percentile
- CWE
- CWE-532
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · hp
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| hp | poly videoos | cpe:2.3:o:hp:poly_videoos |
| hp | poly eagleeye cube | cpe:2.3:h:hp:poly_eagleeye_cube |
| hp | poly eagleeye iv | cpe:2.3:h:hp:poly_eagleeye_iv |
| hp | poly studio a2 | cpe:2.3:h:hp:poly_studio_a2 |
| hp | poly studio e60 | cpe:2.3:h:hp:poly_studio_e60 |
| hp | poly studio e70 | cpe:2.3:h:hp:poly_studio_e70 |
| hp | poly studio g62 | cpe:2.3:h:hp:poly_studio_g62 |
| hp | poly studio g7500 | cpe:2.3:h:hp:poly_studio_g7500 |
| hp | poly studio usb | cpe:2.3:h:hp:poly_studio_usb |
| hp | poly studio x30 | cpe:2.3:h:hp:poly_studio_x30 |
| hp | poly studio x32 | cpe:2.3:h:hp:poly_studio_x32 |
| hp | poly studio x50 | cpe:2.3:h:hp:poly_studio_x50 |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp poly tcosbefore 6.6.1-7001859
- hp poly videoosbefore 4.6.1-444242
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hp). Independent of NVD's CPE analysis and usually ahead of it.
HP Inc Poly EagleEye Cube
- before <PolyOS 4.6.1-444242affected
HP Inc Poly G7500
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio A2
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio E60
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio E70
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio G62
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio USB
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio X30
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio X32
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio X50
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio X52
- before <PolyOS 4.6.1-444242affected
HP Inc Poly Studio X70
- before <PolyOS 4.6.1-444242affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.