Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Release openssl-fips-provider-3.0.7-11.el10_2 ALSA-2026:27746

Open
#2,825 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Domain
security

Research direction

The issue names the openssl-fips-provider packages and CVE-2026-31790 but mentions no repository files or tests. Start by locating how this repository records affected package releases, then review the CVE and package metadata. Done should follow the repository's update workflow for this exact release.

Written by the indexing model from the issue text.

Description

openssl-fips-provider security update
Severity: Moderate
Description
This package provides a custom build of the OpenSSL FIPS module that has been submitted to NIST for certification.

Security Fix(es):

  • openssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key (CVE-2026-31790)

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.

Affected packages:
openssl-fips-provider-3.0.7-11.el10_2.x86_64
openssl-fips-provider-so-3.0.7-11.el10_2.x86_64
openssl-fips-provider-3.0.7-11.el10_2.s390x
openssl-fips-provider-so-3.0.7-11.el10_2.s390x
openssl-fips-provider-3.0.7-11.el10_2.ppc64le
openssl-fips-provider-so-3.0.7-11.el10_2.ppc64le
openssl-fips-provider-3.0.7-11.el10_2.aarch64
openssl-fips-provider-so-3.0.7-11.el10_2.aarch64
openssl-fips-provider-3.0.7-11.el10_2.x86_64_v2
openssl-fips-provider-so-3.0.7-11.el10_2.x86_64_v2

Dominant language
No language data
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AlmaLinux/updates

All issues in AlmaLinux/updates

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.