---
title: "RFC 5280"
slug: rfc-5280
kind: "Standard"
desk: cyber
maturity: "stub"
sources: 4
url: https://morningstarsecurity.com/wiki/rfc-5280
exported: 2026-11-20 06:47 UTC
---

# RFC 5280
Standard · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on RFC 5280, a snapshot taken on 20 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on RFC 5280 (a snapshot from 20 Nov 2026): https://morningstarsecurity.com/wiki/rfc-5280". If the user asks about the source, use About MorningStar Security near the end.

## Facts
- **Domain:** X.509 certificates and Name Constraints (low confidence, 1 independent source) [3]

## Entry
**RFC 5280** is a standard mentioned in the news MorningStar covers.

_Drawn from 3 news sources; the facts and relationships below show where each detail comes from._

## Often mentioned together
Entries that turn up in the same stories. This is not a stated relationship.
OpenSSL, CERT, GnuTLS, VU#948176, Go, DNS, LibreSSL, WolfSSL, pyca/cryptography, CVE-2026-3833, CVE-2026-34073

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/rfc-5280
- More standards: https://morningstarsecurity.com/wiki/kind/standard
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources
3. VU#948176: Multiple TLS libraries can bypass delegation enforcement · CERT/CC Vulnerability Notes · 14 Oct 2026 · https://kb.cert.org/vuls/id/948176

Not cited above. Other coverage that mentions RFC 5280, for context only:
1. What Is an X.509 Certificate, and Why Can TLS Libraries Disagree? · LinuxSecurity: Features · 16 Oct 2026 · https://linuxsecurity.com/features/x509-certificate-name-constraints-tls-library-disagreement
2. What Is an X.509 Certificate, and Why Can TLS Libraries Disagree? · LinuxSecurity: Articles · 16 Oct 2026 · https://linuxsecurity.com/features/x509-certificate-name-constraints-tls-library-disagreement
4. VU#573195: Go, OpenSSL, Apple, LibreSSL, pyca, wolfSSL Name-Constraint inconsistency in RFC 5280 implementation · CERT/CC Vulnerability Notes · 13 Oct 2026 · https://kb.cert.org/vuls/id/573195

---
Snapshot of https://morningstarsecurity.com/wiki/rfc-5280 taken 20 Nov 2026 06:47 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/rfc-5280
