Skip to content
Tools / authgear-server / Security

Security Deep Dive

authgear-server

Security posture and CVE patch evidence from tracked releases.

Back to Tool

3 high-severity dependency CVEs affects 2026-05-06.0.

Review the dependency vulnerabilities below.

— Signed — SLSA ✓ SBOM ✓ Security policy Monthly cadence · 28d median Active maintainer

Trust Signals — 4 of 9 Present

Evidence already collected from releases and repository metadata.

4/9 Present
Signed releases Unknown
Latest release artifact signature Latest release
SLSA provenance Unknown
Attestation predicate level Latest release
SBOM published Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 23d ago
Release cadence: monthly Present
28d median over recent releases Release history
Latest release: 28d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 2d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 28d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 28d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 28d ago
6.8/10 Security Score
6.3/10 Scorecard
Dependency Exposure 6 transitive dependency CVEs found in the latest SBOM.

Security Score

A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.

epss

0.25 / 0.5

No EPSS data

freshness

1.00 / 1.0

2d stale

scorecard

2.52 / 4.0

Score 6.3/10

cve health

1.75 / 2.5

No open CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-0.67 / 10.0

Risk 6.7/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

7.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

9.3

10%

supply chain risk: 6.73 transitive cves: 0c/3h

Provenance trust

provenance trust

6.3

40%

scorecard score: 6.3 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 2d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none
How is this calculated?

The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.

Supply Chain Risk

Risk 6.7/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
63% Dependency freshness

Scorecard

Scorecard 6.3/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check Score Reason
Maintained 10 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Code-Review 10 all changesets reviewed
Security-Policy 10 security policy file detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Packaging -1 packaging workflow not detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
License 10 license file detected
Binary-Artifacts 10 no binaries found in the repo
Branch-Protection -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Signed-Releases 0 Project has not signed or included provenance with any releases.
Fuzzing 10 project is fuzzed
SAST 0 SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies 2 dependency not pinned by hash detected -- score normalized to 2

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

3460 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

0

High

3

Medium

2

Low

0

Unknown

1

High 3 Medium 2 Unknown 1
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-44665 high fast-xml-builder 1.1.5
CVE-2026-6321 high fast-uri 3.0.6
CVE-2026-6322 high fast-uri 3.0.6
CVE-2026-42338 medium ip-address 10.1.0
CVE-2026-44664 medium fast-xml-builder 1.1.5
CVE-2026-33814 unknown golang.org/x/net v0.52.0

Showing 6 of 6

Beta — feedback welcome: [email protected]