diff --git a/.github/workflows/osv-scanner-pr.yml b/.github/workflows/osv-scanner-pr.yml
index 4d5c4475f..c7238a97b 100644
--- a/.github/workflows/osv-scanner-pr.yml
+++ b/.github/workflows/osv-scanner-pr.yml
@@ -39,3 +39,13 @@ jobs:
       # (medium_or_higher), not by failing this check. Keep the check green
       # so it only supplies the analysis; the ruleset decides blocking.
       fail-on-vuln: false
+      # RELIABILITY: resolve Maven parent POMs through Google's byte-identical
+      # Maven Central mirror instead of repo.maven.apache.org, which
+      # intermittently 429s during transitive resolution (e.g.
+      # spring-boot-starter-parent). Same maven2 layout, same bytes -> no
+      # coverage loss; transitive scanning stays fully enabled. See
+      # security-scan.yml for the full rationale.
+      scan-args: |-
+        --maven-registry=https://maven-central.storage-download.googleapis.com/maven2
+        -r
+        ./
diff --git a/.github/workflows/security-scan.yml b/.github/workflows/security-scan.yml
index 7a077b05c..05c96a339 100644
--- a/.github/workflows/security-scan.yml
+++ b/.github/workflows/security-scan.yml
@@ -57,6 +57,23 @@ jobs:
       security-events: write
     with:
       fail-on-vuln: true
+      # RELIABILITY: point Maven transitive (parent-POM) resolution at Google's
+      # byte-identical Maven Central mirror instead of repo.maven.apache.org.
+      # osv-scanner resolves parent POMs (e.g. spring-boot-starter-parent) over
+      # its own HTTP client (osv-scalibr pomxmlnet -> defaultRegistry.URL); the
+      # canonical Central host intermittently returns HTTP 429, which failed this
+      # required gate on APPROVED Maven PRs with "No issues found" (a network
+      # flake, not a real vuln). The mirror serves the same maven2 layout and the
+      # same bytes, so coverage is unchanged -- this ONLY swaps the default
+      # registry host. Repos' own pom.xml <repositories> are still added on top
+      # (scalibr AddRegistry), and transitive scanning stays fully enabled (no
+      # --no-resolve). Caching ~/.m2 or a settings.xml <mirror> would NOT help:
+      # osv-scanner never reads ~/.m2/repository and parses settings.xml only for
+      # <servers> auth, not <mirrors>. --maven-registry is the only effective lever.
+      scan-args: |-
+        --maven-registry=https://maven-central.storage-download.googleapis.com/maven2
+        -r
+        ./
 
   dependency-review:
     if: github.event.action != 'closed'