Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2016-8938

IBM UrbanCode Deploy could allow a user to execute code using a specially crafted file upload that would replace code on the server. This…

Critical10.0EPSS 2.8%
Published
Updated
Reserved
Assigned by
ibm

Description

IBM UrbanCode Deploy could allow a user to execute code using a specially crafted file upload that would replace code on the server. This code could be executed on the UCD agent machines that host customer's production applications.

Timeline

  1. ID reserved

    By ibm

  2. · 3 months later

    Published

  3. · 8 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2016-8938, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.0Critical10.0CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
2.8% · top 13% of all CVEs (8 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 10.0.

Weakness

Affected products

  • IBM Corporation · UrbanCode Deploy

    • affected 6.1.0.2
    • affected 6.0
    • affected 6.0.1
    • affected 6.0.1.1
    • affected 6.0.1.2
    • affected 6.0.1.3
    • affected 6.0.1.4
    • affected 6.0.1.5
    • affected 6.0.1.6
    • affected 6.1
    • affected 6.1.0.1
    • affected 6.1.0.3
    • affected 6.0.1.7
    • affected 6.0.1.8
    • affected 6.1.0.4
    • affected 6.1.1
    • affected 6.1.1.1
    • affected 6.1.1.2
    • affected 6.1.1.3
    • affected 6.1.1.4
    • affected 6.1.1.5
    • affected 6.0.1.9
    • affected 6.1.1.6
    • affected 6.1.1.7
    • affected 6.1.2
    • affected 6.0.1.10
    • affected 6.0.1.11
    • affected 6.1.1.8
    • affected 6.1.3
    • affected 6.1.3.1
    • affected 6.2
    • affected 6.2.0.1
    • affected 6.0.1.12
    • affected 6.1.3.2
    • affected 6.2.0.2
    • affected 6.2.1
    • affected 6.0.1.13
    • affected 6.2.1.1
    • affected 6.0.1.14
    • affected 6.1.3.3
    • and 2 more

References (2)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2016-8938 badge
[![CVE-2016-8938](https://cveledger.app/badge/CVE-2016-8938.svg)](https://cveledger.app/cve/CVE-2016-8938)

Record last updated .