Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-111487medium4.3

Out-of-bounds write vulnerability in the assimp scene import plugin of Qt3D impacts Qt Framework

Impact

An out-of-bounds write vulnerability in the Qt Framework assimp scene import plugin of the Qt3D module.

Source excerpt · Qt

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

qt · Qt

Qt Framework

3 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

6.5.0 → before 6.8.10

python versions

6.9.0 → before 6.11.3

python versions

6.12.0 → before 6.12.1

python versions

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:2.3:a:qt:qt:*:*:*:*:*:*:*:*cpe:2.3:a:qt:qt3d:*:*:*:*:*:*:*:*

Original source description

An out-of-bounds write vulnerability in the Qt Framework assimp scene import plugin of the Qt3D module.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-111487

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-787 ↗

CWE-787 Out-of-bounds Write

Qt

Related →
Contributing organizations · 1
Qt

Assigning organization

2026-10-30

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources