Repository scan
tarmo
GispoCoding/tarmo · branch main · scanned 25 Jun 2026 · 97 resources
High 145
High 138 known vulnerabilities in unknown@unknown (postgis/postgis:16-master)
How to fix
No fixed version of unknown is available yet. Check whether postgis/postgis:16-master needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2026-48962 fixed in no fix yet
- High CVE-2025-58187 fixed in no fix yet
- High CVE-2025-58188 fixed in no fix yet
- High CVE-2025-61723 fixed in no fix yet
- High CVE-2025-61725 fixed in no fix yet
- High CVE-2025-61726 fixed in no fix yet
- High CVE-2025-61729 fixed in no fix yet
- High CVE-2026-32280 fixed in no fix yet
- High CVE-2026-32281 fixed in no fix yet
- High CVE-2026-32283 fixed in no fix yet
- High CVE-2026-33814 fixed in no fix yet
- High CVE-2026-39820 fixed in no fix yet
- High CVE-2026-48959 fixed in no fix yet
- High CVE-2026-12087 fixed in no fix yet
- High CVE-2025-68121 fixed in no fix yet
- Medium CVE-2025-45582 fixed in no fix yet
- Medium CVE-2025-58183 fixed in no fix yet
- Medium CVE-2026-50219 fixed in no fix yet
- Medium CVE-2025-47912 fixed in no fix yet
- Medium CVE-2025-58186 fixed in no fix yet
- and 118 more
High 6 known vulnerabilities in stdlib@1.24.6 (postgis/postgis:16-master)
How to fix
Update stdlib from 1.24.6 to 1.25.8 or later in postgis/postgis:16-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.25.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-33811 fixed in 1.25.10
- High CVE-2026-39836 fixed in 1.25.10
- High CVE-2026-42499 fixed in 1.25.10
- High CVE-2026-42504 fixed in 1.25.11
- Medium CVE-2025-58185 fixed in 1.24.8
High Expensive NAT Gateway
NAT Gateways are expensive managed services. Ensure they are strictly necessary.
How to fix
Consider using VPC Endpoints, NAT Instances for non-critical workloads, or share a single NAT Gateway across multiple subnets.
Where
Medium 100
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit
Ensure that AWS Lambda function is configured for function-level concurrent execution limit
Where
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)
Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)
Where
Medium Ensure that CloudWatch Log Group is encrypted by KMS
Ensure that CloudWatch Log Group is encrypted by KMS
Where
Medium Check encryption settings for Lambda environmental variable
Check encryption settings for Lambda environmental variable
Where
Medium Ensure AWS Lambda function is configured to validate code-signing
Ensure AWS Lambda function is configured to validate code-signing
Where
Medium Ensure CloudWatch log groups retains logs for at least 1 year
Ensure CloudWatch log groups retains logs for at least 1 year
Where
Medium X-Ray tracing is enabled for Lambda
X-Ray tracing is enabled for Lambda
Where
Medium Ensure Secrets Manager secrets should have automatic rotation enabled
Ensure Secrets Manager secrets should have automatic rotation enabled
Where
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK
Ensure that Secrets Manager secret is encrypted using KMS CMK
Where
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Where
Medium Ensure VPC subnets do not assign public IP by default
Ensure VPC subnets do not assign public IP by default
Where
Medium Ensure every security group and rule has a description
Ensure every security group and rule has a description
Where
Medium Missing Cost and Usage Report
No AWS Cost and Usage Report (CUR) configured. CUR provides detailed cost tracking and analysis.
How to fix
Enable AWS Cost and Usage Reports to track spending patterns and identify optimization opportunities.
Where
Medium Ensure VPC flow logging is enabled in all VPCs
Medium Ensure the default security group of every VPC restricts all traffic
Ensure the default security group of every VPC restricts all traffic
Where
Medium Ensure public facing ALB are protected by WAF
Medium Ensure CloudFront distribution has a response headers policy attached
Ensure CloudFront distribution has a response headers policy attached
Where
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability
Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability
Where
Medium Ensure RDS instance with copy tags to snapshots is enabled
Ensure RDS instance with copy tags to snapshots is enabled
Where
Medium Ensure that an S3 bucket has a lifecycle configuration
Ensure that an S3 bucket has a lifecycle configuration
Where
Medium Ensure S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
Medium Ensure AWS RDS database instance configured with encryption in transit
Ensure AWS RDS database instance configured with encryption in transit
Where
Medium Ensure AWS Load Balancers use strong ciphers
Medium Ensure that load balancer is using at least TLS 1.2
Ensure that load balancer is using at least TLS 1.2
Where
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances
Ensure that enhanced monitoring is enabled for Amazon RDS instances
Where
Medium Ensure that detailed monitoring is enabled for EC2 instances
Ensure that detailed monitoring is enabled for EC2 instances
Where
Medium Ensure that ALB drops HTTP headers
Medium Ensure that EC2 is EBS optimized
Medium Ensure that S3 bucket has cross-region replication enabled
Ensure that S3 bucket has cross-region replication enabled
Where
Medium Ensure that S3 buckets are encrypted with KMS by default
Ensure that S3 buckets are encrypted with KMS by default
Where
Medium Ensure that Load Balancer has deletion protection enabled
Ensure that Load Balancer has deletion protection enabled
Where
Medium Ensure that RDS instances have Multi-AZ enabled
Medium Ensure all data stored in the RDS is securely encrypted at rest
Ensure all data stored in the RDS is securely encrypted at rest
Where
Medium Ensure RDS database has IAM authentication enabled
Medium Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher
Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher
Where
Medium Ensure the S3 bucket has access logging enabled
Medium Ensure DB instance gets all minor upgrades automatically
Medium Ensure Create before destroy for ACM certificates
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22
Ensure no security groups allow ingress from 0.0.0.0:0 to port 22
Where
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80
Ensure no security groups allow ingress from 0.0.0.0:0 to port 80
Where
and 14 more groups with 14 findings
Low 16
Low 7 known vulnerabilities in be_BY@latin (postgis/postgis:16-master)
How to fix
No fixed version of be_BY is available yet. Check whether postgis/postgis:16-master needs be_BY at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2010-4756 fixed in no fix yet
- Low CVE-2018-20796 fixed in no fix yet
- Low CVE-2019-1010022 fixed in no fix yet
- Low CVE-2019-1010023 fixed in no fix yet
- Low CVE-2019-1010024 fixed in no fix yet
- Low CVE-2019-1010025 fixed in no fix yet
- Low CVE-2019-9192 fixed in no fix yet
Low 5 known vulnerabilities in hdf5@1.14.5%2Brepack-3 (postgis/postgis:16-master)
How to fix
No fixed version of hdf5 is available yet. Check whether postgis/postgis:16-master needs hdf5 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2018-14034 fixed in no fix yet
- Low CVE-2018-14035 fixed in no fix yet
- Low CVE-2021-45829 fixed in no fix yet
- Low CVE-2025-44904 fixed in no fix yet
- Low CVE-2025-44905 fixed in no fix yet
Low 2 known vulnerabilities in tiff@4.7.0-3%2Bdeb13u2 (postgis/postgis:16-master)
How to fix
No fixed version of tiff is available yet. Check whether postgis/postgis:16-master needs tiff at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2018-10126 fixed in no fix yet
- Low CVE-2024-6716 fixed in no fix yet
Low Missing AWS Budget
No AWS budget configured. Budgets help monitor and control spending with alerts.
How to fix
Create AWS budgets with alerts for forecasted and actual costs to avoid unexpected charges.
Where
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 25 Jun 2026; it may have changed since.
Scan your own repository
InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.