BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2017
CVE-2016-10009High confidence

Affected product: Untrusted Search Path

Unknown · Unknown

7.3HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 29 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 37.43% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainopensshVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.4_p1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainopensshVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.4_p1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainopensshVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.4_p1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourceopensshVendor fix publishedDebian records a fixed source-package version for this release.1:7.4p1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceopensshVendor fix publishedDebian records a fixed source-package version for this release.1:7.4p1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourceopensshVendor fix publishedDebian records a fixed source-package version for this release.1:7.4p1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceopensshVendor fix publishedDebian records a fixed source-package version for this release.1:7.4p1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
2NGA002579 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2016-10009
2 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ABB M2M Gateway ARM600, firmware versions >=4.1.2|<=5.0.3
  • ABB M2M Gateway SW, software versions >=5.0.1|<=5.0.3
Summary
Untrusted search path vulnerability in ssh-agent.c in ssh-agent in OpenSSH before 7.4 allows remote attackers to execute arbitrary local PKCS#11 modules by leveraging control over a forwarded agent socket.
Remediation
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2016-1206

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Untrusted search path vulnerability in ssh-agent.c in ssh-agent in OpenSSH before 7.4 allows remote attackers to execute arbitrary local PKCS#11 modules by leveraging control over a forwarded agent-socket.

What

Untrusted search path vulnerability in ssh-agent.c in ssh-agent in OpenSSH before 7.4 allows remote attackers to execute arbitrary local PKCS#11 modules by leveraging control over a forwarded agent-socket.

Why

The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Untrusted search path vulnerability in ssh-agent.c in ssh-agent in OpenSSH before 7.4 allows remote attackers to execute arbitrary local PKCS#11 modules by leveraging control over a forwarded agent-socket.

Why

The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Untrusted Search Path → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-426 ↗

CWE-426: Untrusted Search Path. The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-426Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-1996OpenSSH: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in OpenSSH ausnutzen, um beliebigen Programmcode mit den Rechten des Dienstes auszuführen, seine Privilegien zu erweitern oder einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV17-039Multiple Apple security updates

585, CVE-2016-7922, CVE-2016-7923, CVE-2016-7924, CVE-2016-7925, CVE-2016-7926, CVE-2016-7927, CVE-2016-7928, CVE-2016-7929, CVE-2016-7930, CVE-2016-7931, CVE-2016-7932, CVE-2016-7933, CVE-2016-7934, CVE-2016-7935, CVE-2016-7936, CVE-2016-7937, CVE-2016-7938, CVE-2016-7939, CVE-2016-7940, CVE-2016-7973, CVE-2016-7974, CVE-2016-7975, CVE-2016-7983, CVE-2016-7984, CVE-2016-7985, CVE-2016-7986, CVE-2016-7992, CVE-2016-7993, CVE-2016-8574, CVE-2016-8575, CVE-2016-8740, CVE-2016-8743, CVE-2016-9533, CVE-2016-9535, CVE-2016-9536, CVE-2016-9537, CVE-2016-9538, CVE-2016-9539, CVE-2016-9540, CVE-2016-9586, CVE-2016-9642, CVE-2016-9643, CVE-2016-9935, CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012, CVE-2016-10158, CVE-2016-10159, CVE-2016-10160, CVE-2016-10161, CVE-2017-2364, CVE-2017-2367, CVE-2017-2376, CVE-2017-2377, CVE-2017-2378, CVE-2017-2379, CVE-2017-2380, CVE-2017-2381, CVE-2017-2382, CVE-2017-2384, CVE-2017-2385, CVE-2017-2386, CVE-2017-2389, CVE-2017-2390, CVE-2017-2391, CVE-2017-2392, CVE-2017-2393, CVE-2017-2394, CVE-2017-2395, CVE-2017-2396, CVE-2017-2397, CVE-2017-2398, CVE-2017-2399, CVE-2017-2400, CVE-2017-2401, CVE-2017-2402, CVE-2017-2403, CVE-2017-2404, CVE-2017-2405, CVE-2017-2406, CVE-2017-2407, CVE-2017-2408, CVE-2017-2409, CVE-2017-2410, CVE-2017-2412, CVE-2017-24

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0297Multiples vulnérabilités dans Juniper

0387?language=en_US Bulletin de sécurité Juniper JSA79188 du 10 avril 2024 https://supportportal.juniper.net/s/article/2024-04-Security-Bulletin-Junos-OS-MX-Series-with-SPC3-and-SRX-Series-When-IPsec-authentication-is-configured-with-hmac-sha-384-and-hmac-sha-512-no-authentication-of-traffic-is-performed-CVE-2024-30391?language=en_US Référence CVE CVE-2011-1089 https://www.cve.org/CVERecord?id=CVE-2011-1089 Référence CVE CVE-2011-1675 https://www.cve.org/CVERecord?id=CVE-2011-1675 Référence CVE CVE-2011-1676 https://www.cve.org/CVERecord?id=CVE-2011-1676 Référence CVE CVE-2011-1677 https://www.cve.org/CVERecord?id=CVE-2011-1677 Référence CVE CVE-2016-10009 https://www.cve.org/CVERecord?id=CVE-2016-10009 Référence CVE CVE-2016-2781 https://www.cve.org/CVERecord?id=CVE-2016-2781 Référence CVE CVE-2017-18018 https://www.cve.org/CVERecord?id=CVE-2017-18018 Référence CVE CVE-2018-1000120 https://www.cve.org/CVERecord?id=CVE-2018-1000120 Référence CVE CVE-2018-1000122 https://www.cve.org/CVERecord?id=CVE-2018-1000122 Référence CVE CVE-2018-1000215 https://www.cve.org/CVERecord?id=CVE-2018-1000215 Référence CVE CVE-2018-1000654 https://www.cve.org/CVERecord?id=CVE-2018-1000654 Référence CVE CVE-2018-20225 https://www.cve.org/CVERecord?id=CVE-2018-20225 Référence CVE CVE-2018-20482 https://www.cve.org

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0027Multiples vulnérabilités dans les produits Juniper Networks

lletin de sécurité Juniper JSA75755 du 10 janvier 2024 https://supportportal.juniper.net/s/article/2024-01-Security-Bulletin-Junos-OS-and-Junos-OS-Evolved-A-specific-query-via-DREND-causes-rpd-crash-CVE-2024-21614 Bulletin de sécurité Juniper JSA75757 du 10 janvier 2024 https://supportportal.juniper.net/s/article/2024-01-Security-Bulletin-Junos-OS-Processing-of-a-specific-SIP-packet-causes-NAT-IP-allocation-to-fail-CVE-2024-21616 Bulletin de sécurité Juniper JSA75758 du 10 janvier 2024 https://supportportal.juniper.net/s/article/2024-01-Security-Bulletin-Junos-OS-BGP-flap-on-NSR-enabled-devices-causes-memory-leak-CVE-2024-21617 Référence CVE CVE-2016-10009 https://www.cve.org/CVERecord?id=CVE-2016-10009 Référence CVE CVE-2016-2183 https://www.cve.org/CVERecord?id=CVE-2016-2183 Référence CVE CVE-2019-17571 https://www.cve.org/CVERecord?id=CVE-2019-17571 Référence CVE CVE-2020-0465 https://www.cve.org/CVERecord?id=CVE-2020-0465 Référence CVE CVE-2020-0466 https://www.cve.org/CVERecord?id=CVE-2020-0466 Référence CVE CVE-2020-12321 https://www.cve.org/CVERecord?id=CVE-2020-12321 Référence CVE CVE-2020-9493 https://www.cve.org/CVERecord?id=CVE-2020-9493 Référence CVE CVE-2021-0920 https://www.cve.org/CVERecord?id=CVE-2021-0920 Référence CVE CVE-2021-25220 https://www.cve.org/CVERecord?id=CVE-2021-2

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-1094Multiples vulnérabilités dans les produits Siemens

.cve.org/CVERecord?id=CVE-2016-0703 Référence CVE CVE-2016-0704 https://www.cve.org/CVERecord?id=CVE-2016-0704 Référence CVE CVE-2016-0705 https://www.cve.org/CVERecord?id=CVE-2016-0705 Référence CVE CVE-2016-0777 https://www.cve.org/CVERecord?id=CVE-2016-0777 Référence CVE CVE-2016-0778 https://www.cve.org/CVERecord?id=CVE-2016-0778 Référence CVE CVE-2016-0797 https://www.cve.org/CVERecord?id=CVE-2016-0797 Référence CVE CVE-2016-0798 https://www.cve.org/CVERecord?id=CVE-2016-0798 Référence CVE CVE-2016-0799 https://www.cve.org/CVERecord?id=CVE-2016-0799 Référence CVE CVE-2016-0800 https://www.cve.org/CVERecord?id=CVE-2016-0800 Référence CVE CVE-2016-10009 https://www.cve.org/CVERecord?id=CVE-2016-10009 Référence CVE CVE-2016-10010 https://www.cve.org/CVERecord?id=CVE-2016-10010 Référence CVE CVE-2016-10011 https://www.cve.org/CVERecord?id=CVE-2016-10011 Référence CVE CVE-2016-10012 https://www.cve.org/CVERecord?id=CVE-2016-10012 Référence CVE CVE-2016-1907 https://www.cve.org/CVERecord?id=CVE-2016-1907 Référence CVE CVE-2016-1908 https://www.cve.org/CVERecord?id=CVE-2016-1908 Référence CVE CVE-2016-2105 https://www.cve.org/CVERecord?id=CVE-2016-2105 Référence CVE CVE-2016-2106 https://www.cve.org/CVERecord?id=CVE-2016-2106 Référence CVE CVE-2016-2107 https://www.cve.org/CVERecord?id=CVE-2016-

Official advisory ↗
CERT-FR · French · CERTFR-2019-AVI-500Multiples vulnérabilités dans les produits Juniper

De multiples vulnérabilités ont été découvertes dans les produits Juniper. Certaines d'entre elles permettent à un attaquant de provoquer un déni de service à distance, un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-487Multiples vulnérabilités dans les produits Juniper

De multiples vulnérabilités ont été découvertes dans les produits Juniper. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une exécution de code arbitraire et un déni de service à distance.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2016-006607OpenSSH の ssh-agent の ssh-agent.c における任意のローカルの PKCS#11 モジュールを実行される脆弱性

OpenSSH の ssh-agent の ssh-agent.c には、検索パスに関する処理に不備があるため、任意のローカルの PKCS#11 モジュールを実行される脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
04

Evidence and provenance

Published 5 Jan 2017 · Last source change 29 May 2026, 20:23 UTC · CWE-426 · Untrusted Search Path

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2016-1206
Product sourceVendor CSAF · ABB Product Security Incident Response Team (PSIRT)
Remediation sourceVendor CSAF · ABB Product Security Incident Response Team (PSIRT)
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2016-1206 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2016-1206"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/9476ce1dd37d3c3218d5640b74c34c65e5f4efe5; added remediation: github.com/9476ce1dd37d3c3218d5640b74c34c65e5f4efe5; removed vendor advisory: access.redhat.com/RHSA-2017:2029; removed vendor advisory: security.freebsd.org/FreeBSD-SA-17:01.openssh.asc; 1 further removals.
    Before
    vendor advisory: access.redhat.com/RHSA-2017:2029 · vendor advisory: security.freebsd.org/FreeBSD-SA-17:01.openssh.asc · vendor advisory: usn.ubuntu.com/3538-1
    After
    patch: github.com/9476ce1dd37d3c3218d5640b74c34c65e5f4efe5 · remediation: github.com/9476ce1dd37d3c3218d5640b74c34c65e5f4efe5
    github.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    github.com ↗
  5. Public exploit evidencePublic exploit evidence changed from Public exploit reference to Public exploit reference.
    Before
    Public exploit reference
    After
    Public exploit reference
    CVE.org ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2016-1206↗Vendor CSAF · ABB Product Security Incident Response Team (PSIRT)↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2016-10009 · cve.blacktree.nl