rlsa-2026:42887
Vulnerability from osv_rocky
Published
2026-07-26 06:01
Modified
2026-07-26 18:07
Summary
Important: java-17-openjdk security update
Details

The java-17-openjdk packages provide the OpenJDK 17 Java Runtime Environment and the OpenJDK 17 Java Software Development Kit.

Security Fix(es):

  • JDK: Enhance TLS certificate handling (CVE-2026-46968)

  • JDK: Improve DTLS handshaking (CVE-2026-46917)

  • JDK: Enhance JPEG handling (CVE-2026-47010)

  • JDK: Enhance XBM image support (CVE-2026-47021)

  • JDK: Enhance Jar file processing (CVE-2026-47027)

  • JDK: Improve certification checking (CVE-2026-60147)

  • JDK: Enhance AWT ImagingLib (CVE-2026-47059)

  • JDK: Enhance Jar handling (CVE-2026-47063)

  • JDK: Update LCMS to 2.19 (CVE-2026-41254)

Enhancement(s):

  • For the last couple of years, OpenJDK has used a single build shared among multiple RPMs and a tarball available on the customer portal. The single "portable" build has a release number ('p') and each RPM has its own release number ('r'). However, the RPM naming only showed the RPM release number, while the version output from the build showed the portable release number, making it unclear that they were different numbers. From this release onwards, a release field of the form 'p.r' is always used for RPMs and the version output shows 'p'. (Rocky Linux-212474, Rocky Linux-212475, Rocky Linux-212476, Rocky Linux-212477, Rocky Linux-212478, Rocky Linux-212479, Rocky Linux-212480, Rocky Linux-212481)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Credits
Rocky Enterprise Software Foundation
Red Hat
References
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Rocky Linux:8",
        "name": "java-17-openjdk",
        "purl": "pkg:rpm/rocky-linux/java-17-openjdk?distro=rocky-linux-8\u0026epoch=1"
      },
      "ranges": [
        {
          "database_specific": {
            "yum_repository": "AppStream"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1:17.0.20.0.8-1.1.el8_10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "credits": [
    {
      "name": "Rocky Enterprise Software Foundation"
    },
    {
      "name": "Red Hat"
    }
  ],
  "details": "The java-17-openjdk packages provide the OpenJDK 17 Java Runtime Environment and the OpenJDK 17 Java Software Development Kit.\n\nSecurity Fix(es):\n\n* JDK: Enhance TLS certificate handling (CVE-2026-46968)\n\n* JDK: Improve DTLS handshaking (CVE-2026-46917)\n\n* JDK: Enhance JPEG handling (CVE-2026-47010)\n\n* JDK: Enhance XBM image support (CVE-2026-47021)\n\n* JDK: Enhance Jar file processing (CVE-2026-47027)\n\n* JDK: Improve certification checking (CVE-2026-60147)\n\n* JDK: Enhance AWT ImagingLib (CVE-2026-47059)\n\n* JDK: Enhance Jar handling (CVE-2026-47063)\n\n* JDK: Update LCMS to 2.19 (CVE-2026-41254)\n\nEnhancement(s):\n\n* For the last couple of years, OpenJDK has used a single build shared among multiple RPMs and a tarball available on the customer portal.  The single \"portable\" build has a release number (\u0027p\u0027) and each RPM has its own release number (\u0027r\u0027).  However, the RPM naming only showed the RPM release number, while the version output from the build showed the portable release number, making it unclear that they were different numbers.  From this release onwards, a release field of the form \u0027p.r\u0027 is always used for RPMs and the version output shows \u0027p\u0027. (Rocky Linux-212474, Rocky Linux-212475, Rocky Linux-212476, Rocky Linux-212477, Rocky Linux-212478, Rocky Linux-212479, Rocky Linux-212480, Rocky Linux-212481)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.",
  "id": "RLSA-2026:42887",
  "modified": "2026-07-26T18:07:48.965627Z",
  "published": "2026-07-26T06:01:06.667800Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://errata.rockylinux.org/RLSA-2026:42887"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2459420"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2502751"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2502782"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2502783"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2502784"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2502791"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2502792"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2502793"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2503636"
    }
  ],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Important: java-17-openjdk security update",
  "upstream": [
    "CVE-2026-41254",
    "CVE-2026-46917",
    "CVE-2026-46968",
    "CVE-2026-47010",
    "CVE-2026-47021",
    "CVE-2026-47027",
    "CVE-2026-47059",
    "CVE-2026-47063",
    "CVE-2026-60147"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.