Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Resources Downloaded over Insecure Protocol in igniteui

CVE-2016-10552GHSA-2r5h-gh4x-8hp9

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm igniteui

    Affected
    <= 0.0.5
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2016-10552: 0.53% estimated exploitation activity in the next 30 days; percentile 44.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Affected versions of igniteui download Javascript and CSS resources over an unencrypted HTTP connection. An attacker with a privileged network position can intercept and view or modify any content sent or recieved over an unencrypted HTTP connection. Recommendation The igniteui package has been deprecated by the package author and now exists under ignite-ui, which should be used in place of this package.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-2r5h-gh4x-8hp9

  2. Revision 1 · created ·

    Published from osv record GHSA-2r5h-gh4x-8hp9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2016-10552

Advisory: Resources Downloaded over Insecure Protocol in igniteui
IDs: CVE-2016-10552, GHSA-2r5h-gh4x-8hp9
Record: https://patchnext.com/advisories/cve-2016-10552 (revision 2, source checked 26 Oct 2026, 12:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm igniteui: affected <= 0.0.5

## Suggested inspection (read-only)
- `npm ls igniteui --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on igniteui.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2r5h-gh4x-8hp9 (OSV record GHSA-2r5h-gh4x-8hp9 lists affected ranges: npm igniteui >=0 <=0.0.5)
- Verified: https://github.com/advisories/GHSA-2r5h-gh4x-8hp9 (GitHub-reviewed advisory GHSA-2r5h-gh4x-8hp9 lists affected ranges: npm igniteui >=0 <=0.0.5)

Commands are suggestions: review each one before running it.

Loading voting…